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

The description adds substantial behavioral context beyond the annotations: it discloses the tool replaces the ENTIRE page body and does not merge/append, it documents ETag-based concurrent-edit safety handling, and it states the required env vars and PAT scope (Wiki: Read & Write). This is exactly the kind of destructive-context and auth detail an agent needs. No contradiction with readOnlyHint=false, destructiveHint=true, or idempotentHint=true.

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?

Four dense sentences, each earning its place: scope constraint, core action, critical edit-vs-replace warning, concurrency safety, and auth prerequisites. The most decision-relevant information is front-loaded ('AZURE DEVOPS ONLY', create/overwrite, call get_page first). Zero fluff 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 write tool, the description covers everything an agent needs to select and invoke it correctly: prerequisites (env vars + PAT scope), safety mechanism (ETag), destructive scope (entire body replaced), and routing to sibling tools. All four parameters are documented in the schema. The only omission is return-value format, which is minor for an upsert tool and not required given no output schema.

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 baseline is 3 — the schema already documents all four parameters with examples, fallback behavior, and disambiguation guidance. The description adds minimal parameter-specific meaning beyond the schema, only lightly reinforcing that content is 'new markdown content.' It does not need to compensate, so 3 is appropriate.

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 states a specific action ('Create a new wiki page, or OVERWRITE an existing one with new markdown content') tied to a concrete resource. It also distinguishes itself from sibling tools by explicitly naming ado_wiki_get_page as the tool to call first for edits, and the scope constraint 'AZURE DEVOPS ONLY' anchors it against non-DevOps siblings.

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?

Explicit when-to-use guidance is present: 'ALWAYS call ado_wiki_get_page first if you intend to edit (not replace) an existing page's content.' This routes the agent to the correct alternative with a clear condition. It also routes to ado_wiki_list for the wikiIdentifier disambiguation case. This is model-level usage guidance.

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