update_customer

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

The description implies a mutation operation but lacks details on behavior: what happens if customer_id is invalid, whether partial updates are supported, or if missing optional fields reset to defaults. No annotations are provided to supplement this.

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 short (5 words) but at the expense of necessary detail. It lacks structure and fails to convey critical information, making it under-specified rather than 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 tool has 4 parameters, 0% schema coverage, and no annotations, the description is grossly inadequate. It does not cover the purpose of each field, expected behavior on partial updates, or the output schema (though the output schema exists).

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?

Schema description coverage is 0%, and the description does not explain any parameters. The agent must infer that 'email', 'first_name', 'last_name' are updatable fields, but no additional meaning is provided beyond the keys.

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 'Update a customer's profile fields' clearly indicates the verb 'Update' and the resource 'customer's profile fields'. It distinguishes from sibling tools like create_customer and delete_customer, though it does not explicitly differentiate from other update-like tools.

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 usage guidelines are provided. The description does not specify when to use this tool, prerequisites (e.g., customer must already exist), or when to prefer alternatives like create_customer.

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