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

Annotations indicate this is not read-only and not destructive, but the description adds no behavioral context beyond the basic 'create' action. It does not disclose effects on QuickBooks, required permissions, validation behavior, or what response to expect, so the description contributes little beyond what the annotations already imply.

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 clear sentence with no filler, tautology, or redundant detail. It is appropriately front-loaded and easy to parse quickly.

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 schema covers parameters well, but the overall definition lacks sibling differentiation, usage context, and behavioral expectations. An agent can likely invoke the tool in a straightforward case, but it is not fully equipped to choose this tool correctly or understand side effects without additional inference.

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 input schema fully documents the entity object and the optional company parameter. The description adds no parameter-level detail, but the baseline of 3 applies because the structured schema carries the burden.

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 names a specific verb ('Create'), a clear resource ('a credit memo'), and the platform ('QuickBooks Online'), so an agent can identify what the tool does. It does not, however, differentiate this from closely related create_* siblings such as create_refund_receipt or create_vendor_credit, so it stops short of full sibling differentiation.

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 gives no guidance on when to use this tool versus alternatives like send_credit_memo, update_credit_memo, create_refund_receipt, or create_credit_card_payment_txn. There is no mention of prerequisites, when a credit memo is the right transaction type, or when to choose another create tool.

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