invoices_list_estimates

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to repeat those. However, it adds no behavioral context beyond that—no mention of return format, pagination, data scope, or any constraints. With annotations present, the bar is lower, but the description contributes nothing extra.

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 extremely terse—just 'List Estimates'—which is concise but under-specified. It lacks necessary details to be appropriately sized; while it has no wasted words, it also has no substance. The lack of structure makes it feel incomplete rather than efficiently minimal.

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 9 parameters, no output schema, and a two-word description, the tool is severely under-documented. The agent has no idea what the response looks like, how to interpret results, or how to set up pagination effectively. This is inadequate for a tool of this complexity.

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?

The schema description coverage is 100%, with each of the 9 parameters having a description in the schema. The tool description provides no additional meaning, so the baseline of 3 applies. It neither adds nor subtracts from the schema's documentation.

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 the verb 'List' and the resource 'Estimates', which is clear but does not differentiate from siblings such as invoices_list_estimate_templates or invoices_list_invoices. The name itself carries the meaning, but the description adds no additional specificity or scope.

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 provides no guidance on when to use this tool versus alternatives, no context about filtering or when not to use it. There is no mention of the tool's purpose in a broader workflow, leaving the agent without any decision support.

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