autotask_get_invoice_details

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

No annotations are provided, so the description carries the full burden. It states the tool returns an invoice with nested line items, which implies a read operation. However, it does not disclose any other behavioral traits such as required permissions, error handling, or rate limits. This is adequate but not rich for a simple get tool.

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 with no redundant information. The first sentence defines the action and resource, the second provides usage context. Every word adds value.

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 tool is a simple get operation with one parameter and no output schema, the description is complete enough. It explains what is returned (invoice with nested line items). It could mention error scenarios for invalid IDs, but this is not necessary for core understanding.

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%: the only parameter, invoiceId, has a clear description in the schema. The tool description does not add extra meaning beyond what the schema provides, so the baseline score of 3 applies.

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 action ('Get'), the resource ('single Autotask invoice'), and adds specificity with 'nested line items'. This distinguishes it from sibling tools like autotask_search_invoices, which returns a list, and other get tools for different entities.

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 a context ('finance workflows that need to see exactly what an invoice contains'), implying when to use it. However, it does not explicitly mention when not to use it or directly reference the alternative autotask_search_invoices for searching invoices.

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