qbo_purchases_update

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

With no annotations, the description carries full burden. It correctly communicates it is a mutating operation (update) and the sparse nature (only provided fields changed). It does not disclose details like side effects or error states but is sufficient for basic understanding.

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?

Two sentences effectively communicate core functionality and constraint. It is front-loaded and avoids redundancy. Could be slightly improved by structuring prerequisites but remains efficient.

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?

Missing output schema description or hints about return value. The description does not cover error conditions or validation. For a complex tool with 9 parameters and nested objects, more context would be beneficial.

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 descriptions exist for all parameters. The description adds no new semantic info beyond reinforcing the sparse-update behavior. Baseline 3 is appropriate as the description does not significantly enhance parameter understanding.

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 verb 'sparse-update' and the resource 'Purchase record', distinguishing it from create and retrieve operations. It specifies the unique behavior: only provided fields are changed.

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 explains the sparse-update concept, implying only changed fields should be sent. It also mentions required Id and SyncToken. However, it does not explicitly compare to sibling tools like qbo_purchases_create or prerequisites like fetching SyncToken first.

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