autotask_get_invoice_details

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

No annotations are provided, so the description must disclose behavior. It mentions 'nested line items' and that it fetches a single record, which helps. However, it does not state whether this is a read-only operation, any authentication needs, or rate limits. The description is neutral but adds value beyond 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 a single sentence that is front-loaded with the main purpose, followed by a usage hint. It is concise and efficient, though the second part could be integrated more cleanly.

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 this is a simple retrieval tool with one parameter and no output schema, the description provides adequate context (nested line items, finance workflows). It could mention that invoice ID is required or clarify if any error handling occurs, but it's sufficient for a straightforward tool.

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% with one parameter (invoiceId) described as 'The invoice ID to fetch'. The description adds no additional semantic meaning to the parameter beyond what the schema already provides, so baseline 3 is appropriate.

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 fetches a single Autotask invoice with nested line items, using a specific verb ('Get') and resource ('Autotask invoice'). It distinguishes itself from sibling tools like autotask_search_invoices which would search for multiple invoices, but does not explicitly name that sibling.

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 mentions 'finance workflows' as a use case, giving some context, but does not provide explicit guidance on when not to use this tool or when to use alternatives like autotask_search_invoices for listing invoices.

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