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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds genuinely useful behavioral context beyond that: deals are private to the API-key owner (data scoping), results are sorted newest first, and the response includes aggregated forecast totals. 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?

Two sentences with zero waste. The core purpose and sorting detail are front-loaded, followed by filtering options and the privacy caveat. Every sentence earns its place.

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 low-complexity tool with two optional parameters, no output schema, and annotations covering the safety profile, the description is nearly complete: it covers scope, ordering, the forecast aggregation, and privacy. A brief note on the response shape would fully close the gap, but nothing an agent needs to call it correctly is missing.

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 coverage is 100%, so the schema already documents both parameters ('Optional stage filter' and 'Optional: only deals linked to this lead'), including the full enum for stage. The description merely names stage and lead_id without adding format, semantics, or interaction details beyond what the schema provides, so the baseline 3 applies.

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 verb+resource ('List the caller's sales deals') with distinctive details (newest first, weighted pipeline forecast with open/weighted/won totals) that set it apart from get_deal and get_sales_analytics. However, it never names a sibling or explicitly differentiates, so it earns 4 rather than 5.

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 implies its use case (listing deals and viewing pipeline forecast totals) and notes optional filters, but it gives no explicit when-to-use vs. alternatives, no exclusions, and no pointer to get_deal for single-deal lookup or get_sales_analytics for broader analytics. Usage context is implied, not stated.

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