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

The description adds no behavioral context beyond what the annotations already convey: it simply says 'Create,' matching the readOnlyHint=false annotation. It does not disclose side effects on accounting records, whether the operation is reversible, idempotency, or error conditions. No contradiction with annotations exists.

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. It communicates the essential operation and platform efficiently, and every word contributes to the meaning.

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 simple create operation with a detailed input schema, this is minimally adequate. The description lacks usage guidance, expected return behavior, and side-effect awareness, but the schema covers the critical entity details. Given no output schema and a nested object parameter, more context would help an agent invoke it correctly.

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 tool description provides no parameter-level meaning, but the input schema has 100% coverage and already describes the VendorCredit entity and the optional company parameter. The entity schema adds useful context about prohibited sensitive fields, so the baseline of 3 is appropriate.

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 operation: 'Create a vendor credit in QuickBooks Online.' It identifies a specific verb and resource and adds the platform context. However, it does not differentiate this tool from related create tools like create_credit_memo or create_bill, so it stops short of full 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?

There is no guidance on when to use this tool versus alternatives, no prerequisites (e.g., vendor must exist), and no mention of related read/update/delete operations. An agent must infer usage solely from the tool name and generic create pattern.

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