autotask_search_ticket_charges

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

No annotations are provided, so the description carries the full burden. It discloses a critical behavioral trait: without a ticketId, results are capped at 10, which overrides the schema's pageSize maximum of 100. This adds essential context beyond the schema.

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: one sentence and two short statements. Every word contributes meaning, no redundancy.

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?

While the description covers the input usage well, it lacks any information about what the output contains (e.g., fields, structure). Given there is no output schema, the agent must infer the return format from the tool name and context. This is a gap for completeness.

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% with descriptions for both parameters. The description adds value by emphasizing 'Provide ticketId for best performance' and 'Max 10 if unfiltered,' which aids parameter selection and clarifies constraints not in 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 clearly states the tool's purpose: 'Search ticket charges (materials, costs, expenses).' The verb 'search' and resource 'ticket charges' are precise, and the parenthetical explains what charges include. Among siblings, there is a distinct 'get' tool for single retrieval, so this search tool is well-differentiated.

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 advises to 'Provide ticketId for best performance' and notes 'Max 10 if unfiltered,' giving clear guidance on when to use the tool and what to expect. It does not explicitly mention alternatives, but the context of it being a search tool versus other entity-specific tools is implied.

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