update_estimate

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

With no annotations, the description carries full burden for transparency. It only states 'update,' indicating mutation, but does not disclose behavioral traits such as idempotency, required permissions, error scenarios, or whether the tool returns the updated estimate. Minimal information leaves agents uncertain about side effects.

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 a single short sentence but is under-informative. It lacks front-loading of key details and does not structure information beyond the basic action-object pair. Conciseness here sacrifices utility.

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 of updating an accounting estimate (nested object, multiple possible fields) and the absence of output schema or annotations, the description is severely incomplete. It does not address return values, error handling, or typical scenarios, making it insufficient for reliable agent invocation.

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 50% (only 'company' has a description). The critical 'params.estimate' object has no description or type definition, and the tool description adds no meaning. The agent has no insight into the structure or required fields of the estimate data.

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 ('update') and the resource ('estimate in QuickBooks Online'). It distinguishes itself from sibling tools like create_estimate and delete_estimate by implying modification of an existing estimate. However, it lacks details on scoping or specific fields that can be updated.

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 vs. alternatives like create_estimate or other update tools. There is no mention of prerequisites (e.g., estimate must exist), context of use, or exclusions.

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