quickbooks_sync_to_qbo

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

Annotations already indicate destructive and idempotent behavior. The description adds the de-duplication behavior ('QBO creates are de-duplicated against prior successful syncs') and required scopes, which goes beyond the annotations. No contradictions found.

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 three sentences, front-loaded with the primary action, and every sentence adds value. No fluff or repetition of schema details.

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?

The description covers selection modes, prerequisites, scopes, and de-duplication. No output schema exists, but the tool is a straightforward sync action. It lacks explicit error handling info, but the description is sufficient for an agent to invoke it.

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 coverage is 100%, so baseline is 3. The description adds meaning by specifying the 'exactly one of' constraint among transactionId, transactionIds, and all, and the 50-item limit for transactionIds. This goes beyond the individual parameter descriptions in the 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 clearly states the action: 'Push EDI transactions INTO QuickBooks Online' with specific transaction types (810 Invoice, 850 Bill, 835 Payment). It distinguishes from sibling tools like quickbooks_export_to_edi (which likely does the reverse direction) and send_outbound_document (which sends documents to trading partners).

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 explicit usage context: 'Provide exactly one of: transactionId (one), transactionIds (up to 50), or all:true'. It also states required prerequisites (confirm:true, idempotencyKey) and scopes. It does not explicitly mention alternatives or when not to use, but the context is clear.

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