update_account

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. It only states 'update,' implying mutation, but fails to specify whether fields are overwritten or merged, required permissions, rate limits, or side effects. This is insufficient for safe usage.

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 extremely brief (one sentence plus 'FREE'), but this conciseness comes at the cost of completeness. For a tool with six parameters, the description should include more context to be useful. It is under-specified rather than efficiently concise.

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 lack of an output schema, six parameters, and no annotations, the description is far from complete. It does not explain return values, error conditions, what fields can be updated, or how the update behaves with partial inputs. The agent cannot reliably use this tool based solely on the description.

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?

With schema description coverage at only 17% (only account_id has a description), the description adds no additional meaning for the five other parameters (name, domain, phone_number, raw_address, owner_id). The text does not explain their formats, constraints, or relationships. This leaves the agent with inadequate information.

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 'existing account in your Apollo CRM,' which distinguishes it from sibling tools like create_account (create) and search_accounts (search). The mention of 'FREE' is extraneous but does not detract from clarity.

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 on when to use this tool versus alternatives such as create_account or update_contact. No prerequisites, conditions, or exclusions are provided, leaving the agent uncertain about the appropriate context for invocation.

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