quickbooks_list_terms

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

With no annotations, the description solely bears the burden of disclosing behavior. It only mentions routing under JWT/tenant/company scope (common to all such tools) but does not state whether the operation is read-only, destructive, rate-limited, or what the response contains. This is insufficient for safe agent invocation.

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 short (3 sentences) and front-loaded with the operation name. However, most content is boilerplate about routing and argument format, which could be more concise if it focused on domain-specific details. It is not overly verbose, but it lacks substantive content.

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?

Given the complexity (many sibling tools, no schema descriptions, and output schema exists but unaddressed), the description is incomplete. It fails to explain the domain concept of 'terms', the expected arguments, or the return value nature. An output schema exists but provides no context, and the description does not compensate.

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 single parameter 'arguments' is described as 'JSON string of arguments for the connector operation', which barely adds meaning beyond the schema. With 0% schema description coverage, the description should specify expected JSON keys or structure, but it does not, leaving the agent uninformed about how to construct the argument.

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 it is a list operation for 'terms' and identifies the platform tool name, providing verb+resource clarity. However, it does not explain what QuickBooks 'terms' are (e.g., payment terms) or distinguish it from other QuickBooks list tools like list_accounts or list_customers, which all share similar generic descriptions.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks any indication of prerequisites, context, or exclusions, leaving the agent without clues for selection among many sibling QuickBooks list tools.

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