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

Annotations declare readOnlyHint=true, so the safety profile is covered. The description adds the GET endpoint which is redundant with readOnlyHint but confirms the read semantics. It does not disclose pagination defaults, response shape, or filtering limits beyond what annotations and schema state.

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?

Single tight sentence with the verb and resource front-loaded, followed by a note on filtering and the API endpoint. Efficient with no wasted prose, though the endpoint reference is somewhat redundant.

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 an 8-parameter list tool with readOnlyHint and full schema coverage, the description covers the essential purpose and filtering. However, it doesn't clarify relationship to siblings (get_quote, list_invoices) or pagination behavior, leaving a gap for an agent choosing between tools.

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 all 8 parameters are already documented in the schema. The description mentions client and status filtering but adds no syntax or semantics beyond that. Baseline 3 is appropriate given the schema does the heavy lifting.

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 (list) and resource (quotes), and clarifies the synonym 'estimates' which is helpful given the domain. Sibling differentiation is not explicit, though 'list quotes' vs 'get quote' is distinguishable by name. Solid but no explicit sibling comparison.

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 mentions filterability but gives no guidance on when to use this vs get_quote for a single quote, or list_invoices. It does not state when-not-to-use or alternatives. Only implied usage at best.

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