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

Annotations already cover readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety behavior is known. The description adds the endpoint 'GET /estimates' and a list of filterable fields, but does not disclose pagination behavior, rate limits, authentication needs, or match-type behavior beyond what the schema already states.

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 two short sentences, front-loaded with the tool's purpose and immediately followed by supported filters and the HTTP endpoint. There is no repetition or wasted text.

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 25-parameter list tool with 100% schema coverage and no output schema, the description gives the core purpose and filter scope. Pagination, sorting, field selection, and expansion are omitted from the description but fully documented in the schema, leaving only minor contextual gaps.

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 every parameter is already documented with type, format, and match semantics. The description only restates a subset of filter fields and adds no format or matching detail beyond the schema, so 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 and resource: 'List estimates (quotes).' It is clearly distinguishable from create_estimate and get_estimate because it is the list operation, though it does not explicitly name those siblings or contrast the use case.

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 phrase 'Filter by status, number, PO number, customer...' implies the tool is used for filtered estimate searches, but there is no explicit guidance on when to use this instead of get_estimate or how to handle pagination. Usage is implied rather than prescribed.

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