update_business_info

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

No annotations are provided, so the description carries full burden. The [mutation] tag indicates a write operation, but no details are given on side effects, rollback, permissions, or idempotency. The description focuses on the purpose rather than behavioral traits.

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 brief (two sentences plus a [mutation] tag) and front-loaded with the purpose. The second sentence provides context on the value of updating. No redundant information, but could be slightly more structured (e.g., separating behavior from purpose).

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?

For a simple tool with 3 well-documented parameters and no output schema, the description is nearly complete. It explains what fields are updated and why, fulfilling the needs for invocation. However, missing usage guidelines and behavioral details slightly reduce completeness.

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?

Input schema coverage is 100% and each parameter has a clear description and enums. The description merely re-lists the fields without adding meaning beyond the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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 uses a specific verb ('Actualizar') and identifies the resource ('informacion del negocio'). It lists the exact fields updated (business type, sale type, description), clearly distinguishing this tool from siblings like 'update_business_name' and 'update_billing_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?

The description implies usage by stating the information helps AI give more relevant responses, but it does not explicitly specify when to use this tool versus alternatives or provide any exclusions. No guidance on prerequisites or when not to use is given.

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