update_customer

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

With no annotations provided, the description carries the full burden of disclosing behavior. 'Update' implies mutation, but the description does not state whether permissions are required, if updates are reversible, what happens if the customer does not exist, or how errors are handled. This lack of detail leaves the agent 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 sentence with no wasted words, achieving conciseness. However, it is arguably too brief, sacrificing necessary detail. While front-loading is adequate, the sentence fails to cover important aspects, so it is not optimally structured.

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 QuickBooks and the presence of many sibling tools, the description is insufficient. It does not explain how to identify the customer (e.g., by ID), what fields are updatable, or provide any return value expectations. With no output schema, the agent is left without a clear picture of the tool's full behavior.

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?

The schema has 50% description coverage (only 'company' has a description). The 'params' object is undocumented in both schema and description, leaving agents to guess its structure. The description adds no meaning beyond the schema, failing to clarify what properties the customer object should contain.

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 'Update', the resource 'existing customer', and the system 'QuickBooks Online'. It distinguishes from sibling tools like 'create_customer' and 'delete_customer' by indicating modification of an existing record. However, it does not specify which customer fields can be updated, leaving some ambiguity.

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 provides no guidance on when to use this tool versus alternatives, such as when a customer should be created or deleted instead. No prerequisites, context, or exclusion criteria are mentioned, making it difficult for an agent to decide when to invoke this tool.

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