billing_get_invoice

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that it returns invoice details including line items, but does not mention authentication needs, error behavior, or an explicit read-only guarantee. The description mostly restates the tool's name and adds only minimal return information.

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 compact and well-structured with labeled Args and Returns sections. Every line adds information: the core action, the parameter meaning, and what the caller can expect back. There is no filler.

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?

The tool is simple—one required parameter and an output schema—so the basics are present. However, it lacks usage guidance and behavioral context, which could lead an agent to confuse it with billing_list_invoice_items or to call it without understanding when it is the appropriate choice.

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 provides no parameter description (0% coverage), and the description supplies only 'The invoice ID' for invoice_id. This gives a minimal semantic anchor but does not explain where to obtain the ID or any expected format, so it only partially compensates for the schema gap.

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 details') and the resource ('a specific invoice'), making it distinguishable from list-style billing tools. However, it does not explicitly differentiate itself from sibling tools like billing_list_invoices or billing_list_invoice_items, so it falls just short of full sibling distinction.

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?

No guidance is given on when to use this tool versus alternatives such as billing_list_invoices or billing_list_invoice_items. There are no prerequisites, exclusions, or explicit routing cues beyond the phrase 'specific invoice'.

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