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

Annotations already declare `readOnlyHint: true`, `openWorldHint: true`, and `destructiveHint: false`, so the safety profile is covered. The description adds useful context that the result is paged and that returned address IDs are usable as `to`/`from`, but it does not cover auth, rate limits, or exact filtering semantics.

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 four short phrases with zero waste, front-loading the resource, filterability, paging, and endpoint. Every sentence earns its place.

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 list tool with nine optional parameters, no output schema, and low schema description coverage, the description is adequate but sparse. It explains the resource, paging, filters, and ID usability, but does not fully describe the return shape or filtering match behavior.

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 22%, so the description needs to compensate. 'Filter by any field' gives meaning to the seven optional string filter parameters, and 'Paged' maps to `page`/`per_page`, but no field-specific semantics or matching behavior are explained.

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 states a specific verb and resource: 'List the address book' of 'saved addresses with ids usable as `to` / `from`.' This clearly distinguishes it from read/write siblings like `shipcloud_get_address` and `shipcloud_create_address`, though it does not explicitly name those alternatives.

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?

The description says 'Filter by any field' and 'Paged,' which implies filtered listing, but it does not state when to use this tool instead of `shipcloud_get_address`, `shipcloud_get_default_address`, or `shipcloud_create_address`. No when-not guidance or prerequisites are provided.

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