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

With no annotations provided, the description carries the behavioral disclosure burden. It clearly warns that explicit user confirmation is ALWAYS required and states the permission prerequisite: 'DEVOPS_PAT with Work Items: Write permission.' It does not describe the return value or side effects beyond creating a comment, but the confirmation and permission details are significant and go beyond a basic mutation description.

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 organized with clear labels (WHEN, PRIORITY TRIGGER, WARNING, Recommended workflow) and is front-loaded with the core purpose. It is somewhat verbose with repeated trigger examples, but each section serves a distinct role and the length is justified by the safety-critical confirmation requirement.

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 mutation tool with no annotations and no output schema, the description covers the essential context: when to use, prerequisites, required confirmation, and a step-by-step workflow. The only notable gap is the absence of any indication of what the tool returns after posting, but the simple post-comment operation makes that less critical.

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 parameters are already fully documented in the schema. The main description adds no additional parameter-level detail beyond referencing the workflow; the useful 'ready-to-post block' hint actually lives in the schema's commentText description, not in the tool description itself.

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 opens with a specific verb and resource: 'post, add, or save a comment to an ADO Work Item.' It distinguishes itself from the sibling `ado_post_pr_comment` by explicitly targeting Work Items rather than PRs, and from `ado_analyze_workitem` by being the follow-up posting action.

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 explicitly states WHEN to use the tool ('user explicitly asks to post, add, or save a comment to an ADO Work Item') and provides a recommended workflow that names the prerequisite sibling `ado_analyze_workitem`. It also gives concrete trigger phrases and the critical instruction to ask for user confirmation before invoking.

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