quickbooks_cdc

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

The annotations declare readOnlyHint=true and destructiveHint=false, but the description says approval_ref is 'Approved platform task UUID when resuming a write.' This introduces write-resumption behavior that contradicts the read-only annotation. Spring verification and governed routing are useful, but the contradiction makes the behavioral picture misleading.

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 compact and front-loaded with the routing constraint, followed by a clean parameter bullet list. There is little filler, though the terseness contributes to the missing purpose information.

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?

Despite having output schema and annotations, the description never says what the CDC operation actually does or when an agent should call it. The write-resumption language further confuses the read-only nature of the tool. For a 7-parameter connector gateway, this is not enough for an agent to invoke it confidently.

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 0%, so the description must compensate, and it does: every parameter receives at least a one-line semantic gloss (project UUID, connector account alias, idempotency key, effect). Some glosses are terse or jargon-heavy, but they add real meaning absent from the input schema.

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 merely restates the tool name as 'Quickbooks connector operation cdc' and never states what the operation does, such as retrieving changed records or exposing a change-data stream. It adds routing/authority context but no verb or outcome, so an agent cannot tell what this tool accomplishes without prior domain knowledge.

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 quickbooks_cdc versus sibling QuickBooks tools or other connector operations. The routing statement is a constraint on how execution happens, not an explanation of when this tool should be selected.

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