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

The description is minimal, providing no behavioral details beyond the fact that it creates a refund receipt. Even though annotations indicate readOnlyHint=false (so the agent knows it's a write operation), the description adds no information about what happens on creation (e.g., whether it affects inventory, requires specific account settings, or if it triggers any side effects). For a mutation tool, this is insufficient.

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, concise sentence that front-loads the primary action. It wastes no words and is easily scannable. However, it could have been slightly more informative without losing conciseness.

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 involves a nested object parameter ('entity') and has no output schema, but the description doesn't explain what response to expect or any validation constraints. It also doesn't mention required fields within the entity object (though that's partly covered in the schema description, but not fully). Given the complexity of QuickBooks entities, the description is thin and omits important context like what constitutes a valid refund receipt.

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 detailed descriptions for both parameters. The 'entity' parameter is well-explained, including what to include or exclude (government identifiers, birth dates, etc.) and naming the DepositToAccountRef field. The 'company' parameter is also adequately described. Because schema coverage is 100%, the description itself doesn't need to add much, but the schema's rich descriptions raise the score.

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 verb and resource ('Create a refund receipt in QuickBooks Online'). It is specific and distinct from tools like create_sales_receipt or create_credit_memo by naming the specific receipt type. However, it doesn't explicitly differentiate it from the sibling create_sales_receipt, which might be confused, but the name itself is clear.

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 like create_sales_receipt or create_credit_memo. The description doesn't mention any prerequisites, such as having an existing customer or the appropriate permissions. An agent would have to infer usage from the tool name and context.

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