Linting Prose in CI

Описание и применение

Проверка описаний инструментов в CI выявила ошибки в контракте, которые приводили к сбоям сборки. Добавление подсказок использования и приведение описаний в согласованность с Bicep исправили проблему, и сборка прошла успешно.

Задача

Wording changes in tool contracts can break agent behavior; they need to be treated like code changes and validated in CI.

Результат

The linter caught contract issues that caused CI failures; fixing wording restored CI success and improved agent telemetry.

Рабочий процесс

• Push commit with linter and contract changes
• GitHub Action runs contract linter
• Linter reports errors for missing provenance, usage cues, token budget, and drift
• Fix commit adds missing clauses and aligns descriptions
• GitHub Action runs linter again
• Linter passes with zero errors and alias warnings
• CI build succeeds

Доказательства

The linter parses the contract straight out of the McpToolTrigger and McpToolProperty attributes, the authoritative copy, the same source the deployed description hash is computed from.

Источник

The fix commit added when-to-call clauses to two tools ... and aligned the three Bicep descriptions with the C#. The build went green, and the budget rule priced the edit: the contract grew from 277 to 302 tokens, 25 tokens for two sentences of disambiguation, well under budget.

Источник