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

Annotations already mark the tool as destructive, idempotent, and non-read-only. The description adds important behavioral detail beyond those hints by revealing the cascading deletion of sub-pages and the exact authentication requirements. No contradiction with annotations exists.

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, with the most important constraints (scope, deletion behavior, prerequisites) front-loaded. Every sentence adds necessary information and there is no filler or repetition of schema content.

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 destructive tool with no output schema, the description provides the essential context: platform restriction, destructive cascade, and required credentials. It could mention what happens on success or error, but the prerequisites and behavior are sufficiently covered for an agent to invoke it 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 description coverage is 100%, so the schema already documents all three parameters, including defaults and fallback behavior. The description does not add parameter-level detail beyond the schema, which is acceptable given full coverage.

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 names a specific verb ('Delete') and resource ('wiki page') and states that sub-pages are also deleted. It clearly distinguishes this from sibling tools like ado_wiki_get_page and ado_wiki_create_or_update_page by describing a destructive operation rather than a read or write.

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 makes the Azure DevOps-only scope explicit and lists required environment variables plus PAT scopes. It doesn't explicitly name alternatives like ado_wiki_create_or_update_page for edits, but the destructive purpose and prerequisites provide clear context for when this tool should be used.

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