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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the mutation nature is already declared. The description adds one genuinely useful behavioral fact absent from the annotations: that the call returns the persisted record with its SyncToken, which matters because there is no output schema. It says nothing about permissions, idempotency, or failure behavior.

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?

Two short sentences with the operation stated first and the return value second; nothing is redundant. It is efficient, though the terseness leaves real gaps rather than being optimally sized for a create 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?

For a create tool with a nested free-form entity object and no output schema, the description at least discloses the return shape (saved record plus SyncToken). It omits error semantics and any hint about required entity fields, but the 100% schema coverage carries most of that burden, making this minimally adequate.

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?

Schema description coverage is 100%, so the schema already documents both the entity payload (including the government-identifier restriction and DepositToAccountRef) and the optional company parameter. The description adds no parameter-level detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Create a refund receipt in QuickBooks Online'), which is clear enough to distinguish from read/update siblings. However, it does not differentiate from the near-neighbor create_sales_receipt, which an agent could easily confuse with a refund receipt.

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 contains no when-to-use guidance, no prerequisites, and no reference to alternatives such as create_sales_receipt or update_refund_receipt. An agent must infer everything about selection from the tool name alone.

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