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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. Beyond that the description adds genuine behavior: results are ordered newest first and 'value' is computed as the highest option's total, a non-obvious semantic an agent could not infer elsewhere. It stops short of describing page-size defaults or whether pagination is exhaustive, which keeps it off a 5.

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 short sentences, front-loaded with the payload shape, followed by the computation note and a single routing instruction. There is no filler and no repetition of schema or annotation 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?

With no output schema, the description does the work of telling the agent what each row contains and how 'value' is derived, and the schema fully documents paging. It is close to complete for a simple two-parameter read tool; only default page size behavior and total-count/termination semantics are left unstated.

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%, with limit bounded 1-100 and defaulted to 25 and cursor tied to next_cursor from the prior call, so the schema carries parameter meaning fully. The description adds nothing about either parameter; the implicit paging hint is only via the sibling concept of estimate_id, not limit/cursor. 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 names the resource (estimates) and adds ordering (newest first) plus the fields returned (customer, pipeline status, value), so an agent knows exactly what a call yields. The verb 'list' is only implicit from the name, but the routing sentence pointing to get_estimate for options and lines clearly separates it from the detail sibling.

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 one useful routing rule — take estimate_id to get_estimate for options and lines — which is real when-to-use guidance. However, it never states what this tool is not for (e.g., that it takes no filters) or when to prefer list_customers/list_jobs context, so guidance is partial and implied rather than explicit.

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