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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true. The description adds valuable context that the operation runs in the background, returns status immediately, and involves eviction plus re-download. This goes beyond the annotations and explains the operational behavior an agent needs to know. A small deduction because it doesn't mention possible failure modes or the full extent of the eviction side effect.

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 longer than average but well-structured: trigger conditions first, then use case, then parameter guidance, then post-call behavior. The multi-language trigger list is lengthy but earns its place by disambiguating user intent. No sentence is redundant, though it could be trimmed slightly without losing value.

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 tool with only one optional parameter and no output schema, this description is fully complete. It explains what happens, why to use it, when to pass `pat`, the asynchronous/background behavior, the immediate status return, and the recommended verification step. An agent has everything it needs to invoke the tool and follow up correctly.

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 coverage is 100%, so the baseline is 3. The description adds semantic nuance beyond the schema by clarifying that `pat` is a one-time override 'for this resync' and explicitly ties it to the cross-org/cross-tenant scenario. This helps the agent decide when to populate the parameter, exceeding what the schema alone provides.

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 states a specific action ('force a full re-download and re-index') and a specific resource ('Azure DevOps custom model'), which makes it unambiguous. Trigger phrases and examples also clarify what user intent maps to this tool, distinguishing it from the many sibling tools that perform queries or other Azure DevOps actions.

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 begins with 'WHEN' and enumerates explicit trigger phrases in both English and French. It also provides a targeted use case (server PAT lacking access), details when to supply the `pat` parameter, and gives follow-up instructions to wait ~60s and call `healthcheck`. This is strong, actionable guidance with no ambiguity.

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