stripe_get_invoice

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

With no annotations, the description carries the burden of disclosing behavioral traits. It only mentions routing and JWT scoping, omitting critical info like that the operation is read-only, idempotent, or what errors may occur (e.g., invalid invoice ID).

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 brief but wastes the first sentence with a redundant restatement of the name. The second sentence about routing is tangential to the tool's function. Though concise, it lacks a clear, front-loaded explanation of what the tool does.

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?

Despite having an output schema, the description fails to explain the input parameter adequately (0% schema coverage). Combined with missing behavioral details, the description is incomplete for an agent to correctly invoke the tool without external knowledge.

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 single parameter 'arguments' is described as a 'JSON string of arguments for the connector operation.' This adds no real meaning beyond the raw schema (which also has no description). The agent is left guessing what keys/values are expected (e.g., an invoice ID).

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 restates the tool name as 'Stripe connector operation get_invoice' but does not explain that it retrieves a specific invoice from Stripe. It fails to differentiate from sibling tools like stripe_list_invoices or xero_get_invoice, leaving the agent unsure of its core function.

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 provided on when to use this tool versus alternatives (e.g., stripe_list_invoices for listing, stripe_create_invoice for creating). The agent receives no context on prerequisites or typical use cases.

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