quickbooks_batch

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

Annotations already declare non-read-only and destructive behavior, and the description adds useful context beyond that: the operation routes only through governed connector authority, the claimed effect is verified by Spring, and writes resumed through approval require an `approval_ref`. This meaningfully supplements the structured annotations without contradicting them.

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 operation identity and routing constraint stated early. The Args list is scannable and each parameter line adds a distinct piece of information without fluff.

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 covering routing and approval semantics, the description does not explain what the batch operation's `arguments` JSON should contain, what operations it can perform, or when an agent should choose this low-level tool over specialized QuickBooks tools. With schema coverage at 0% and no operation-level semantics, the description is not complete enough for an agent to invoke it correctly in a real task.

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 carry parameter meaning. It provides a one-line semantic for all seven parameters, including the fact that `effect` is verified, `idempotency_key` is a stable business-action identity, and `approval_ref` is for resuming a write. The `arguments` parameter remains vague, but the description compensates for the empty schema substantially.

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 identifies the tool as the QuickBooks connector's `batch` operation and emphasizes governed routing, but it never states what the batch operation actually does at a domain level. It is clearer than a pure tautology but does not distinguish the tool from sibling QuickBooks operations like `quickbooks_query` or `quickbooks_cdc`.

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 about when to use this generic batch operation versus the specialized QuickBooks tools, nor are exclusions or alternatives mentioned. The sentence about governed routing describes a constraint, not a usage context.

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