autotask_search_billing_items

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

No annotations are provided, so description carries full burden. It discloses the default page size (25) and the 'Approve and Post' workflow context, but does not detail authorization needs, rate limits, or behavior when no filters are applied (returns all?). Transparency is basic.

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?

Two concise sentences with no redundant information. First sentence states purpose, second provides essential context. Efficient and front-loaded.

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 12 parameters, no required ones, no output schema, and no annotations, the description adequately covers the tool's purpose and default behavior. Could mention pagination details, but overall sufficient.

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. Description adds value by clarifying that billing items are 'approved and posted', which provides context for filters like isInvoiced and postedAfter/Before. It also mentions default page size (25) which is not in 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?

Description clearly states the verb 'Search' and resource 'billing items', and explains what billing items are (approved and posted from the 'Approve and Post' workflow). This distinguishes it from sibling search tools like autotask_search_billing_item_approval_levels.

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?

Description provides context about billing items but does not explicitly state when to use this tool versus other search tools or filters. It lacks 'when not to use' guidance or alternative recommendations, though the entity name alone provides some differentiation.

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