update_repository_description

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds meaningful behavioral context beyond annotations: that description content is sent through stdin and is not audited. This is a useful, non-obvious operational disclosure that signals potential security/privacy implications. It adds value over the structured fields.

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?

Two sentences, no wasted words. The key behavioral notes (stable ID confirmation, stdin transmission, no auditing) are included concisely. Could be slightly more structured but is appropriately sized and efficient.

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?

For a mutation tool with no output schema and low parameter coverage, the description provides core purpose and a key behavioral warning (no audit). However, it doesn't clarify what 'not audited' fully implies operationally, doesn't explain the expectedRepositoryId parameter's role clearly as a safety check, and doesn't specify behavior when description is null (does it clear vs update). It's adequate but has remaining gaps for a 5-parameter tool.

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?

Schema description coverage is only 20% (only 'repository' has a description). The description adds minimal parameter-specific meaning — it doesn't explain the format or semantics of 'description', 'account', 'hostname', or 'expectedRepositoryId' beyond what the schema shows. The 'expectedRepositoryId' parameter's role as a confirmation mechanism is implied but not explicitly tied to the parameters. With low coverage, the description should compensate more but only partially does.

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 uses a specific verb ('Update or clear') with a clear resource ('allowed repository description'), and includes an important prerequisite ('after confirming its stable repository ID'). It is clear about what the tool does, though it doesn't explicitly distinguish from sibling tools, though the name itself is fairly self-explanatory among sibling names.

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 conveys the core action and notes the required prerequisite of confirming the stable repository ID, which is an important usage gate. However, it doesn't explicitly say when to use this versus alternative tools, nor does it provide exclusion criteria or compare with sibling tools.

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