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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations: it requires DEVOPS_ORG_URL and DEVOPS_PAT, uses page-path syntax, and reads immediate sub-page paths. No annotation contradiction 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?

Single sentence with no filler. The environment constraint, main action, path syntax, and auth requirements are all front-loaded and each contributes necessary information.

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 rich annotations and full schema coverage, the description covers the essential context: environment, auth, path syntax, and behavior. With no output schema, it leaves the exact return format unspecified, but 'Read the content' is sufficient for a simple read operation.

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 baseline is 3. The description repeats path syntax examples already present in the schema and adds no additional meaning for project, wikiIdentifier, or includeSubPages.

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?

States a specific read verb and resource: 'Read the content of a wiki page'. The Azure DevOps-only qualifier and the mention of immediate sub-page paths further scope the operation. It does not explicitly distinguish itself from ado_wiki_list, but the read/get semantics make the purpose clear.

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?

Provides clear usage context: Azure DevOps only, required env vars, and wiki page-path syntax. It does not explicitly name alternatives or say when not to use this tool, but the read action naturally separates it from the create/update/delete wiki siblings.

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