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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only the endpoint and hints at returned record contents (customer, status, totals, line items), which is modest but real value given there is no output schema; it says nothing about rate limits, default sort order, or total-result behavior.

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?

One sentence plus the endpoint, front-loaded with the verb and resource. Nothing is wasted, though the parenthetical is the least reliable part of the definition.

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 five-parameter, zero-required list tool with no output schema, the description should clarify search semantics and result shape. It gestures at returned fields but does not explain how free-text search matches, what the default ordering is, or how results relate to the get_estimate sibling.

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 page, limit, search, sort_by, and sort_dir are all documented in the schema itself, making 3 the baseline. The description adds no parameter-level meaning and its parenthetical field list could mislead an agent into expecting structured filters that do not exist.

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?

States a specific verb+resource ('List or search estimates') with the underlying endpoint, which cleanly separates it from the singular fieldpulse_get_estimate sibling. The parenthetical field list (customer, status, totals, line items) is ambiguous about whether those are filters or returned fields, since the schema exposes no such filter parameters.

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?

'List or search' implies bulk retrieval and free-text querying, but the description never states when to use this over fieldpulse_get_estimate or how to combine search with pagination. Usage is left to inference from the verb.

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