Create customer

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing on top: no mention of required credentials, irreversible effects, rate limits, or that creation is non-idempotent. For a destructive, non-idempotent write with zero description contribution, this is a real gap.

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?

A single short sentence with no padding and the verb front-loaded. It is appropriately terse in form, though the brevity comes at the cost of substance rather than from tight editing.

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 10-parameter, nested-object creation tool with no output schema and only 40% schema coverage, one sentence is far from sufficient. Nothing about required inputs, body-flag vs payload exclusivity, store relationship, or the confirmation contract is explained.

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 only 40% across 10 parameters, including a nested JSON:API payload object, so the description is expected to compensate — and it does not. It never explains the flat attributes (name/email/city/region/country), the mutually exclusive payload vs payload_file paths, store_id, account, or confirm.

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?

"Creates a customer with given attributes" states a verb (creates) and resource (customer), but "with given attributes" is filler that adds no information beyond the name and title. It does nothing to distinguish this tool from siblings like update_customer or list_customers beyond what the name already conveys.

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 versus update_customer, when to use the flat body flags versus the payload/payload_file paths, or what the confirm parameter's role means for invocation. The description offers no context or exclusions at all.

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