autotask_search_billing_items

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

Since no annotations are provided, the description carries full burden. It discloses the default page size (25) but does not mention other behavioral traits such as read-only nature, pagination behavior beyond default, sorting, rate limits, or error conditions. The description is adequate but leaves gaps.

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 long, each serving a clear purpose: stating the tool's function and defining billing items with default paging. No unnecessary words or repetition. It is front-loaded and efficient.

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 the absence of an output schema and annotations, the description should explain return values. It does not describe what fields are returned or typical response structure. The high parameter count (12) and no required parameters indicate a need for more context about expected behavior, which is lacking.

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 high (92%), so baseline is 3. The description adds no parameter-specific information beyond what the schema provides (e.g., parameter descriptions are already detailed). It does not compensate for missing parameter descriptions because there are almost none missing.

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 billing items in Autotask, with a specific verb ('Search for') and resource ('billing items'). It distinguishes from sibling search tools (e.g., search_tickets) by specifying 'billing items' and provides context on what billing items represent (approved and posted billable items).

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 does not provide guidance on when to use this tool versus alternatives like autotask_get_billing_item or other search tools. It lacks statements about when not to use it or prerequisites, leaving the agent to infer usage. No explicit exclusions or alternative recommendations are given.

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