autotask_search_invoices

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

No annotations are provided, so the description bears full responsibility for disclosing behavior. It only says 'search,' implying a read-only operation, but does not explicitly state whether the search has side effects, requires authentication, or has limits. The agent lacks critical safety and usage context.

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 a single sentence with minimal waste. It is direct and easy to parse. However, it could include a brief summary of intended use without being longer, so it earns a high score but not perfect due to lack of structure.

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 no output schema and minimal description, the agent is left without understanding return format, pagination behavior beyond pageSize, or default sorting. For a search tool with optional filters, more detail is expected to ensure proper invocation.

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 description coverage is 100%, so each parameter has inline documentation (e.g., 'Filter by company ID', 'Number of results to return'). The description adds no additional meaning beyond 'optional filters.' Baseline 3 is appropriate as 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?

The description clearly states the tool searches for invoices with optional filters, distinguishing it from sibling search tools like autotask_search_companies or autotask_search_contacts. The verb 'search' and resource 'invoices' are specific, making the purpose unambiguous.

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 on when to use this tool versus alternatives, such as autotask_get_invoice_details or autotask_search_billing_items. There are no instructions on prerequisites, when not to use, or how to combine with other tools. The description leaves the agent without contextual cues for selection.

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