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

The readOnlyHint annotation already signals safety; the description adds useful behavioral context by noting the env var requirements, the path syntax constraint, and the fact that immediate sub-page paths are also returned. It does not describe error behavior or output format, but for a read operation this is acceptable.

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 a single dense sentence that front-loads the critical Azure DevOps constraint, states the operation, gives concrete path examples, and mentions required env vars. No filler or redundancy.

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?

Given the low complexity, full schema coverage, and readOnlyHint annotation, the description covers the essential operational details: Azure DevOps scope, path format, env var prerequisites, and the inclusion of sub-page paths. It could mention the exact return structure, but this is not a critical gap for a simple read 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 100%, so the schema already documents all four parameters. The description reinforces path syntax and env var fallbacks but does not add substantial meaning beyond what the schema 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 explicitly states the verb 'Read' and the resource 'wiki page', and further specifies that it returns the page's content plus immediate sub-page paths. This clearly differentiates it from sibling tools like ado_wiki_create_or_update_page, ado_wiki_delete_page, and ado_wiki_list.

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 provides strong usage context: it is confined to Azure DevOps, requires specific env vars, and uses wiki path syntax. It does not explicitly state when to prefer this over sibling tools, but the read-only purpose and syntax guidance make the intended context clear.

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