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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered, but the description adds no behavior beyond those flags. It is silent on the critical question for a destructive update with nested objects: are omitted fields preserved or cleared, and does supplying `origin` replace the whole sub-object? That gap matters most here.

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 compact sentence with zero filler, front-loaded on the verb and resource. It is efficient but so terse that the brevity comes at the cost of coverage rather than enabling it.

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 5-parameter destructive mutation with nested objects, one required id, and no output schema, the description does far too little. An agent cannot tell whether this is a partial or full replace, what is returned, or how origin_is_return interacts with return_address.

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 coverage is 60% and the description's field list ('name, origin or return address') maps roughly onto title/origin/return_address, adding marginal meaning over the schema. It does not explain origin_is_return or the partial-update semantics, though the schema carries descriptions for address_id and most address sub-fields.

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 a specific verb and resource ('Changes a Ship From Address') and enumerates the mutable surfaces (name, origin, return address), which separates it from create_ship_from_address and delete_ship_from_address. It never names a sibling explicitly, so differentiation is inferred rather than stated.

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 when-to-use guidance, no prerequisites, no mention of alternatives such as set_default_ship_from_address or list_ship_from_addresses (which the address_id schema references). An agent must infer that this is the edit path vs. the create/delete/default siblings purely from the name.

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