autotask_get_billing_item

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

The description indicates a read operation ('Get'), but with no annotations provided, it carries the full burden of behavioral disclosure. It does not specify what happens if the ID does not exist, error handling, authentication requirements, or rate limits. The description is minimal but not misleading.

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 a single concise sentence of 8 words. It is front-loaded with the verb and resource, contains no unnecessary words, and is immediately understandable.

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 simple get-by-ID tool with one parameter and no output schema required for understanding the purpose, the description is nearly complete. It could mention behavior on missing IDs or constraints on the ID value, but overall it sufficiently covers the tool's function.

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% (one parameter with description 'The billing item ID to retrieve'). The description adds no additional semantics beyond the schema, so it meets the baseline of 3 without adding value.

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 verb 'Get' and the resource 'detailed information for a specific billing item by ID'. It straightforwardly distinguishes from the sibling tool 'autotask_search_billing_items' which is for searching, by specifying retrieval by a unique ID.

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 implies usage when a specific billing item ID is known, but does not explicitly state when to use this tool versus the alternative 'autotask_search_billing_items' or other get tools. There is no exclusionary guidance, leaving the agent to infer based on the ID parameter.

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