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

The description adds no behavioral detail beyond what the annotations already convey (readOnlyHint=false, destructiveHint=false). It does not disclose return behavior, idempotency, validation, or effects on QuickBooks data. The sensitive-data warning appears only in the schema, not in the description.

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, front-loaded sentence with no filler or redundant wording. It is efficient, though so minimal that it leaves usage and behavioral context to other fields.

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 straightforward create operation, the description plus a fully documented schema gives an agent the essential action and parameters. However, with no output schema and no mention of return values, duplicate handling, or how this relates to update_class/search_classes, the definition is adequate but not rich.

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 both parameters ('entity' and 'company') are documented in the input schema, including the restriction on sending government identifiers and card-processing details. The description itself adds no parameter-level meaning, but the high schema coverage justifies the baseline score.

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 ('Create') and resource ('a class') in the QuickBooks Online context, making the primary function clear. It does not explicitly differentiate from sibling tools like update_class or search_classes, but the verb and resource are specific enough to avoid core ambiguity.

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 about when to choose this tool over update_class, search_classes, get_class, or other create_* tools. The verb 'Create' implies the use case, but the description provides no explicit context, prerequisites, or exclusions.

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