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

No annotations are provided, so the description must disclose behavioral traits. It only states the action without detailing side effects, authentication requirements, idempotency, or error handling. For a mutation tool, this is a significant gap, similar to the update_drive example.

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, clear sentence with no unnecessary words, making it concise and front-loaded. It conveys the core action effectively, though it could be expanded with useful detail without becoming verbose. The structure is appropriate for the tool's simplicity.

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?

Given no annotations, no output schema, and only three loosely specified parameters, the description is insufficient for an agent to correctly invoke the tool. Missing information includes how to identify the invoice, expected payment amount format, and success/failure behavior, leaving critical operational details unaddressed.

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 explain any parameter meanings, formats, or relationships. The parameter names (invoiceId, paymentAmount, customerName) are somewhat self-explanatory, but paymentAmount's string type and the optionality of customerName remain unclear without additional context.

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 'Record a QuickBooks payment' uses a specific verb ('record') and resource ('QuickBooks payment'), clearly distinguishing it from sibling tools like qb_create_invoice (create) and log_expense (expense). It conveys the action unambiguously.

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 implies usage when one needs to record a payment in QuickBooks, but it provides no explicit when-to-use vs alternatives, prerequisites, or exclusions. It matches the 'implied usage' level, as the context is clear from the tool name but not elaborated.

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