search_invoices

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

The description does not disclose any behavioral traits beyond the annotations. It does not mention return format, search semantics, performance characteristics, or side effects. The annotations (readOnlyHint=false) are surprisingly not read-only for a search tool, but the description itself does not clarify this potential inconsistency.

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 concise at two words, which is efficient but lacks any structure or additional context. It is arguably under-specified for a tool with a complex request body and sorting options.

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?

Given there are 4 parameters, no output schema, and the search operation is non-trivial, the description is far from complete. It fails to explain how search criteria are specified in the body, how results are ordered, or what the response contains. An agent would not know how to use this tool effectively.

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 provides full descriptions for all parameters, so the baseline is 3. The description adds no additional meaning about parameters, such as how 'body' is structured or how 'limit' behaves. It relies entirely on the schema.

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' provides a clear verb and resource, indicating the tool searches for invoices. However, it does not differentiate from the sibling tool 'list_invoices', which likely serves a similar purpose, so it lacks distinguishing 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?

No guidance is provided on when to use this tool versus alternatives such as 'list_invoices' or 'search_quotes'. The description does not mention filters, pagination, or any context where search is preferred over list.

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