autotask_search_billing_items

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

With no annotations provided, the description carries the full burden. It discloses that results are paginated (25 per page default), which is useful behavioral context. However, it doesn't mention other important traits like whether this is a read-only operation (implied by 'search'), authentication requirements, rate limits, error handling, or what the return format looks like (no output 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 appropriately concise with two sentences that each add value: the first defines the tool's purpose and domain context, the second provides important behavioral information about pagination. No wasted words, though it could be slightly more structured by separating purpose from constraints.

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?

For a search tool with 12 parameters, 100% schema coverage, but no annotations and no output schema, the description provides adequate basic context (what's being searched and pagination behavior). However, it lacks information about return format, error conditions, and when to use versus sibling tools, leaving some gaps for the agent to infer.

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 the schema already fully documents all 12 parameters. The description adds no parameter-specific information beyond what's in the schema. According to guidelines, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 and explains what billing items represent (approved and posted billable items from the 'Approve and Post' workflow). It specifies the verb 'search' and resource 'billing items' but doesn't explicitly differentiate from sibling tools like autotask_search_invoices or autotask_search_ticket_charges, which might have overlapping domains.

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 no guidance on when to use this tool versus alternatives. With many sibling search tools (e.g., autotask_search_invoices, autotask_search_ticket_charges), there's no indication of when billing item search is appropriate versus other search types, nor any prerequisites or exclusions mentioned.

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