create_refund_receipt

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

No annotations are provided, yet the description fails to disclose behavioral traits such as whether the operation is idempotent, what permissions are needed, rate limits, or what the response contains. For a write operation, this is a significant gap.

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, well-structured sentence that immediately conveys the tool's purpose. It is appropriately concise with no unnecessary words, earning its place as a front-loaded summary.

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 the tool has nested parameters and no output schema, the description is too brief. It omits critical context such as the effect on QuickBooks, whether a refund receipt is linked to an original sale, or what happens to inventory/accounts. A more complete description would greatly improve usability.

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 description adds no additional meaning beyond the parameter names already present in the schema. With schema description coverage reported as 50%, the description should compensate but does not. It does not explain the purpose or constraints of individual parameters like customer_ref or line_items.

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 (create), the resource (refund receipt), and the context (QuickBooks Online), making it unambiguous. It effectively distinguishes from sibling tools like create_invoice or create_credit_memo by naming the specific refund receipt entity.

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 like create_credit_memo or create_vendor_credit. Without context on prerequisites or typical use cases, an agent may struggle to choose the correct tool among many similar refund-related options.

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