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

Annotations already signal a write operation (readOnlyHint: false) and non-destructive intent (destructiveHint: false). The description adds little beyond restating the mutation: it does not mention persistence, side effects, validation behavior, or any other operational traits that the annotations do not already cover. There is no annotation contradiction.

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 very short and free of filler, but it is under-specified to the point of being barely informative. It is concise but not well-rounded; it earns its place only as a minimal restatement of the tool's name.

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?

With no output schema and an open nested object parameter, the agent needs more context about what a Term contains and what a successful creation returns. The description does not provide that context, nor does it reference related tools like get_term or update_term that could help. It is incomplete for a tool that creates a domain-specific object.

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 schema provides robust parameter detail: the entity is described as a 'QuickBooks Online API v3 Term object' with explicit warnings about sensitive data, and the company parameter is explained. The tool description itself adds no parameter meaning, but the schema carries the burden adequately.

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 clear verb and resource: 'Create a term in QuickBooks Online.' It unambiguously identifies the target resource, distinguishing it from sibling create_* tools. However, it does not explain what a QBO 'term' actually is, leaving some ambiguity for an agent unfamiliar with QuickBooks terminology.

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 such as update_term, get_term, or search_terms. There is no context about prerequisites, exclusions, or conditions that would help an agent select this tool over a sibling. The usage context is only implied by the verb 'create.'

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