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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds non-redundant behavioral context: it uses 'KB signals ... combined with ADO history' and returns a per-phase breakdown, confidence level, and risk factors. No contradiction with annotations.

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 structured with WHEN, PRIORITY TRIGGER, purpose, returns, and trigger phrases, which makes it scannable. It is slightly redundant because the WHEN section and the final Triggers list mostly repeat the same example phrases, but overall it stays reasonably lean.

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 3-parameter tool with no output schema, it fully describes what the estimate is based on, what is returned (phase breakdown, KB signals, confidence, risk factors), and how the output can be used. An agent can select and invoke this tool correctly with the information provided.

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 workItemId, project, and focusObjects. The description mentions Work Item IDs via trigger examples but adds no meaning beyond the schema for parameters like focusObjects or project fallback.

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 opening 'EFFORT ESTIMATOR -- Estimate D365 F&O development effort for a Work Item' states a specific verb, target resource, and domain. It is clearly differentiated from sibling tools like ado_analyze_workitem by focusing on hour estimates and phase breakdowns rather than general analysis.

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?

It gives explicit WHEN triggers ('user asks for an effort estimate, chiffrage, or development hours') and a priority instruction to call AFTER ado_analyze_workitem. It does not explicitly state when not to use the tool or name mutually exclusive alternatives, so it falls short of a 5.

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