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

With no annotations provided, the description carries the full behavioral burden and meets it: it discloses that eviction plus download runs in the background, that the tool returns status immediately, and that readiness requires a ~60 second wait. It also surfaces the PAT-override behavior and why it matters.

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 front-loaded with the WHEN condition and triggers, then moves through rationale, parameter use, and post-conditions. The trigger list is long but earns its place for selection accuracy, and no sentence is filler.

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 single optional-parameter tool with no output schema, the description supplies everything an agent needs: purpose, trigger phrases, authentication context, asynchronous behavior, and explicit follow-up verification via healthcheck or search tools.

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% and the schema already explains the pat parameter, so the baseline is high. The description adds the semantic nuance that the PAT is an override 'for this resync,' scoping it to a one-time operation rather than a persistent configuration change.

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 opens with a specific action and object: 'force a full re-download and re-index of their Azure DevOps custom model.' This is unambiguous and clearly differentiates the tool from the other ADO, search, and healthcheck siblings, none of which perform a forced rebuild.

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 explicitly lists trigger phrases ('resync', 'reindex', 'force sync', 'my model is stale') and the PAT-failure scenario where an override is needed. It gives clear context for when to call the tool, though it does not explicitly state a 'do not use when' condition or name a direct alternative.

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