autotask_get_invoice_details

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

No annotations; description reveals nested structure (line items). Does not mention read-only nature, authentication, or error behavior, leaving gaps for an agent.

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?

Two focused sentences: first defines action and resource, second provides usage context. No wasted 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?

Adequately describes input and output (invoice with line items) for a simple get-by-id tool. Lacks explicit note on response format or error cases, but sufficient for typical use.

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 covers the single parameter fully with description 'The invoice ID to fetch'. Tool description adds no further semantic detail beyond schema.

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?

Clearly states fetching a single Autotask invoice with nested line items. Distinguishes from siblings like autotask_search_invoices (list/search) and autotask_get_billing_item (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?

Explicitly recommends use for finance workflows needing full invoice details. Does not explicitly state when not to use, but context implies it's for fetching by ID, not searching.

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