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 implies a read operation (no side effects) but does not explicitly state idempotency, read-only nature, or any rate limits. It is adequate but lacks detailed behavioral disclosure.

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 long, front-loading the action and resource. Every sentence provides necessary information without unnecessary words.

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 single-parameter retrieval tool with no output schema, the description explains what is returned (invoice with nested line items) and the intended use case. It is complete enough but could mention that it is read-only and idempotent.

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?

The input schema has 100% coverage for the single parameter (invoiceId). The description does not add additional semantic meaning beyond the schema's description. It focuses on the output (nested line items) rather than the parameter.

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 'Get a single Autotask invoice with its nested line items', using a specific verb and resource. It distinguishes from sibling tools like autotask_search_invoices (which returns a list) and autotask_get_billing_item (which gets a single billing item).

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 includes a use case: 'Use for finance workflows that need to see exactly what an invoice contains.' This provides context but does not explicitly mention when not to use it or alternatives (e.g., using search_invoices for a summary).

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