List ship-from addresses

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

The annotations already declare this as read-only, idempotent, open-world, and non-destructive. The description adds meaningful behavioral context beyond that by explaining the returned address semantics: ship-from location, return address, origin_is_return when they match, and the default marker. It does not cover pagination or ordering, but with annotations carrying the safety profile this is a solid disclosure.

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 reasonably compact and front-loads the resource plus default-address information. The opening sentence is somewhat redundant with the following explanation, but the content is dense and useful rather than bloated.

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?

With no output schema, the description does a good job explaining the important returned fields and default semantics. It is nearly complete for a zero-parameter list tool, though it could mention whether all addresses are returned or whether pagination/order applies.

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?

The tool has zero parameters, so there are no parameter semantics to document and the baseline is 4. The description correctly does not invent parameter details.

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 clearly identifies the resource as saved Ship From Addresses and explains that it includes return-address information and marks the default. It also distinguishes this read/list operation from related mutation tools by telling the agent to use an id in update_ship_from_address, delete_ship_from_address, or set_default_ship_from_address.

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 gives useful usage context by explaining that returned ids feed into update, delete, and set-default operations. It does not explicitly state when not to use this tool or contrast it with a competing list alternative, but no obvious list alternative exists for this resource.

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