update_company_info

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses nothing beyond "Update" implying mutation. It does not explain that sync_token exists for optimistic concurrency and what happens on a stale token, whether omitted fields are left unchanged (sparse update) or cleared, whether permissions are required, or whether the change is reversible.

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 single sentence is front-loaded and free of filler, so it is maximally concise. However, the brevity comes at the cost of under-specification rather than efficiency — there is simply not enough content to be 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?

This is a mutation tool with no annotations, no output schema, a required nested params object, and no prose covering concurrency, permissions, or partial-update semantics. Given that complexity, one generic sentence is far from complete for an agent to invoke it safely.

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 description adds zero meaning about parameters; the only top-level parameter is an opaque "params" wrapper whose purpose is never explained in prose. The nested schema does label individual fields (id, sync_token, email, company_addr, etc.), but their semantics in the context of an update — especially partial-vs-full update behavior — remain undocumented.

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 says "Update the company information in QuickBooks Online," which conveys a mutation of a company resource, but it is essentially a restatement of the tool name with the platform appended. It gives no hint about which company fields are mutable (name, email, address, phone) and does not distinguish this from the sibling get_company_info.

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?

There is no when-to-use guidance at all: no prerequisites (the company must already exist), no mention that get_company_info should be called first to obtain the required sync_token, and no alternative tools named. The agent must infer all routing from the tool name alone.

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