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

Annotations already indicate this is a mutating operation (readOnlyHint=false, destructiveHint=false), and the description merely restates that by saying 'Create'. It adds no detail about side effects, required permissions, idempotency, or how the created receipt is returned, so it contributes no behavioral transparency beyond structured data.

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, efficient sentence with no filler, and the key verb and resource are front-loaded. While very short, it is structurally clean and easy to parse.

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 tool with a nested entity and many create_* siblings, the description is too sparse to be contextually complete: it does not mention the document type's typical use, what happens after creation, or any relationship to send_sales_receipt. The structured schema fills parameter details, but selection context and workflow are missing.

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% and the entity property is richly documented in the schema, including the warning about government identifiers. The tool description adds no parameter-level meaning of its own, so the baseline score 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 clearly identifies the operation as creating a sales receipt in QuickBooks Online, giving a specific verb and resource. However, it makes no reference to sibling tools like create_invoice or create_credit_memo, so it does not help an agent distinguish when a sales receipt is the right document type.

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 choose this tool over alternatives such as create_invoice, create_credit_memo, or create_refund_receipt, nor any prerequisites or exclusions. The only usage signal is the tool name itself, which is not enough for correct selection.

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