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 only states the action ('create') without revealing any side effects, such as whether the invoice is a draft or sent immediately, required permissions, or what happens on success/failure. This is a significant gap for a mutation tool.

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, direct sentence that is perfectly front-loaded and contains no filler. Every word earns its place, making it an example of excellent conciseness for a simple tool.

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 deceptively simple but has no annotations, no output schema, and undocumented parameters. The description fails to provide any context beyond the bare action, leaving the agent without essential information about required fields (beyond schema), expected behavior, or integration specifics. It is inadequate even for a basic 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?

The input schema has 0% description coverage, and the description does not add any meaning to the parameters (customerName, amount, dueDate, description). The agent is left to infer semantics solely from parameter names, with no guidance on formats, units, or relationships between fields.

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 'Create a QuickBooks invoice' uses a clear verb ('create') and a specific resource ('QuickBooks invoice'), making the tool's purpose immediately obvious. It also naturally distinguishes itself from sibling tools like qb_record_payment and get_quickbooks.

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 provides no guidance on when to use this tool versus alternatives (e.g., qb_record_payment for payments, log_expense for expenses). There is no mention of prerequisites, such as the customer needing to exist in QuickBooks, or any context in which this tool should be preferred. Usage is only implied by the tool name.

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