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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds useful context beyond annotations: the tool depends on specific env vars, targets Azure DevOps specifically, and its result set includes both project wikis and published code-as-wiki repos. No contradictions with annotations.

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?

Every sentence earns its place: scope warning, purpose with detail, explicit usage guidance, and environmental requirements. It is front-loaded with 'AZURE DEVOPS ONLY' and contains no filler or repetition.

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 simple list operation with one optional parameter, rich annotations, and clear usage guidance, the description is complete. It explains when to use the tool, what it returns conceptually, and what environment setup is needed. No critical information is missing.

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 100%: the only parameter, project, is fully described with its optionality and fallback to DEVOPS_PROJECT env var. The tool description does not add parameter-level detail, but the schema already carries that burden, so the baseline 3 applies.

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 ('List') and resource ('all wikis in a project'), and elaborates on what counts as a wiki ('project wiki plus any published code-as-wiki repos'). This clearly distinguishes it from sibling wiki tools like ado_wiki_get_page or ado_wiki_create_or_update_page, which operate on individual pages.

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?

It explicitly tells the agent when to use it: 'Use this FIRST when the user doesn't know the wiki's exact name/id, or to confirm which wiki to target before reading/writing a page.' It also gives environmental prerequisites (env vars) and an 'AZURE DEVOPS ONLY' scope, leaving no ambiguity about invocation context.

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