update_company_info

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

The description indicates a mutation operation ('Update') but provides no additional behavioral context such as required permissions, reversibility, effect on omitted fields, or response behavior. With no annotations, the description fails to disclose important traits beyond the verb.

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 efficient sentence with no filler. However, it lacks front-loading of key constraints or context, and it could be slightly more structured for clarity.

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 tool's complexity (nested object, many updatable fields, concurrency token, no output schema, no annotations), the description is insufficient. It omits important details like partial update semantics, required fields, and return value, leaving gaps for the agent.

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 input schema already provides descriptions for all parameters, including nested fields. The description does not add meaning beyond stating the tool's general purpose. For a tool with high schema coverage, a baseline of 3 is appropriate.

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' and the resource 'company information in QuickBooks Online'. It is specific enough to distinguish from unrelated tools but does not differentiate from other update tools like update_account or update_customer.

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 versus alternatives. For instance, there is no mention of prerequisites, context for use, or when not to use it, leaving the agent to infer 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.