autotask_search_ticket_charges

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

With no annotations, the description implies a read operation but does not detail idempotency, side effects, authentication needs, or return format. The performance tip is helpful but behavioral transparency is limited.

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, front-loaded with the core purpose, and every word adds value. No redundant or unnecessary information.

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 no annotations, the description could more fully explain what the tool returns (e.g., list of charge objects) and pagination details beyond the unfiltered max. It is adequate but not complete.

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 covers 100% of parameters, so baseline is 3. The description adds value by noting performance benefit of ticketId and a constraint ('Max 10 if unfiltered') that overrides pageSize, which is not in the schema. This clarifies behavior beyond 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 searches ticket charges (materials, costs, expenses) with verb 'search' and resource 'ticket charges'. It distinguishes from related tools like get_ticket_charge or create_ticket_charge, but does not differentiate from other search tools among siblings.

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 provides guidance to 'provide ticketId for best performance' and notes 'Max 10 if unfiltered', giving context on when to use the optional parameter. However, it does not explicitly contrast with alternative tools like get_ticket_charge for single record retrieval.

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