set_branch_governance

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already mark the tool as destructive (destructiveHint=true). The description adds context by explaining that setting governance enables evaluation of PR, merge, release, and publish actions against explicit workflow state. This provides behavioral insight beyond the annotation, though it does not detail side effects of clearing or authorization requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single efficient sentence that front-loads the action ('Declare or clear') and explains the purpose. Every word earns its place with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (11 optional parameters, no output schema), the description is too brief. It does not explain that all parameters are optional, how the tool interacts with get_branch_governance, or what return value to expect. More context is needed for an agent to use it effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 11 parameters have individual descriptions in the input schema (100% coverage), so the baseline is 3. The tool description does not add extra parameter meaning beyond the schema, but it is not necessary given the schema's thoroughness.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: declare or clear branch and release governance. It specifies the affected actions (PR, merge, release, publish) and distinguishes from the sibling tool 'get_branch_governance', which retrieves governance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when governance needs to be set or cleared, but it does not provide explicit guidance on when to use this tool versus alternatives (e.g., get_branch_governance) or when not to use it. No exclusions or prerequisites are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.