search_invoices

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering safety. The description adds no additional behavioral context such as pagination behavior, default sorting, or required permissions. It does not contradict annotations.

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 single sentence 'Search invoices.' is extremely concise and front-loaded, but it is under-specified for a tool with 5 parameters and an output schema. It wastes no words but also contributes little beyond the tool name.

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 tool with multiple optional filters, pagination, an output schema, and many sibling tools, the description is inadequate. It does not mention filtering capabilities, search fields, or differences from get_invoice, leaving the agent without enough context to invoke it optimally.

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 has 5 optional parameters with 0% description coverage. The description does not explain how 'query' works, what filters like customer_id or service_location_id do, or how page/per_page function. Parameter names are self-explanatory to a degree, but the description adds no confirmation.

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 'Search invoices' names the verb 'search' and resource 'invoices', but lacks any scope or filtering details, making it vague. It does not explicitly distinguish from sibling get_invoice, though 'search' implies plural or filtered retrieval.

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?

No guidance is provided on when to use this tool versus alternatives like get_invoice or search_customers. There is no mention of query syntax, use cases, or when not to use it.

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