manage-customer-address

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

With no annotations, the description carries the full burden for a mutation tool that includes a delete. It does not say whether delete is permanent, what happens to the customer's default flag when the default address is removed, whether update is a full replacement (the nested address object sets additionalProperties=false), or what permissions are needed.

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?

Two short, front-loaded sentences with no filler; the optional-default behavior is surfaced early rather than buried. It is efficient, if slightly thin for the scope of the operation.

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 five-parameter, nested-object, destructive-capable tool with zero annotation coverage and no output schema, the description leaves too much unsaid: side effects of delete, default-address semantics, and the update replacement model are all absent.

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 100%, including the action enum, the GID formats, and the 'required for create and update' / 'required for update and delete' conditions, so the baseline is 3. The description only restates setAsDefault and adds nothing about action-dependent parameter requirements.

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?

States specific verbs (create/update/delete) against a specific resource (a customer's mailing address), and the action enum in the schema corroborates the three modes. It is clearly distinct from the sibling create-customer/update-customer tools, though it never says so explicitly.

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 reach for this versus update-customer or customer-merge, no prerequisites, and no mention that addressId is mandatory for update/delete or that a default address may need special handling. The only usage signal is the action enum, which is structured data, not description content.

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