post-crm-v3-objects-invoices-search_search

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

With no annotations, the description carries the burden of behavioral disclosure. It adds context with a concrete example and a requirement, but does not disclose whether the operation is read-only, response format, pagination behavior, or auth requirements.

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 two sentences, includes the essential endpoint and a compact example, and is well-structured for quick scanning without unnecessary verbosity.

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?

The schema is detailed, and the description provides an example, but there is no output schema and the description does not explicitly describe response structure or pagination, leaving some gaps for a search tool.

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 the baseline is 3. The description adds an example demonstrating the structure of filterGroups and properties, providing practical semantics beyond the schema descriptions.

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 specifies the HTTP method and endpoint, identifies the resource (invoices) and action (search), and provides an example. It clearly distinguishes from sibling search tools through the path segment 'invoices'.

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 states a requirement ('REQUIRES body parameter with search criteria') and demonstrates usage with an example, but does not explicitly state when to prefer this over batch read or other search operations. No alternatives or exclusions are mentioned.

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