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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the write/safety profile is covered. The description adds a useful return-value detail (saved record with SyncToken), which partly compensates for the missing output schema. It does not disclose failure/idempotency behavior or any permission requirements.

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, front-loaded sentences with zero filler: the action first, then the return payload. Nothing is wasted.

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 definition is minimally adequate: the schema carries the field-level detail and the description notes the returned SyncToken. It is missing the contextual routing information (when to prefer this over sibling create tools) that complexity here would warrant.

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 both the nested 'entity' object and the 'company' parameter are already documented in the schema, including the caution about government identifiers. The description adds no parameter-level meaning beyond that, so the baseline of 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?

The description states a specific verb and resource ('Create a sales receipt in QuickBooks Online'), which is clearly understandable. However, it does nothing to differentiate this from the many adjacent create_* siblings (create_invoice, create_refund_receipt, create_credit_memo, create_estimate), so an agent must rely on external knowledge of QuickBooks object types to choose correctly.

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?

There is no guidance on when to use this tool versus create_invoice, create_refund_receipt, create_payment, or create_deposit, nor any prerequisites (e.g., customer/item must exist, company must be connected). The one relevant hint — the company parameter — is left to the schema only.

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