autotask_get_billing_item

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

The description indicates it retrieves detailed information, but no annotations are provided. It does not disclose behavior like potential errors, authorization needs, or data freshness. However, the description does not contradict any annotations (none present).

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?

Single sentence, concise and front-loaded with key action. Could be slightly more structured but 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?

Tool is simple with one parameter and no output schema, so description is minimally adequate. However, no explanation of what 'detailed information' includes or example usage.

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 one parameter, which already has description 'The billing item ID to retrieve'. The description adds no further meaning beyond the schema, leading to baseline score of 3.

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 uses a specific verb 'Get' with a resource 'billing item' identified by ID, clearly stating the purpose. However, it lacks differentiation from the sibling tool autotask_search_billing_items, which likely retrieves multiple 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?

No explicit guidance on when to use this tool vs autotask_search_billing_items, but the description implies it's for a single item by ID. No prerequisites or context provided.

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