checkout_delivery_addresses

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

With no annotations present the description carries the full burden, and it does disclose one genuinely behavioral fact: login is required. The read-only, non-destructive nature is strongly implied by 'available' and returns are covered by the output schema, but nothing is said about whose addresses are returned or whether an unauthenticated call errors or returns empty.

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 sentences with no wasted words, and the resource statement is front-loaded ahead of the login caveat. It is efficient almost to a fault: the terseness is what leaves the gaps noted elsewhere.

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 zero-parameter read tool with an output schema and no annotations, the description covers the essentials (what it returns, that auth is needed) but omits the one thing that matters most in this sibling set: how these addresses relate to my_addresses and the other checkout_* tools.

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 takes zero parameters and schema coverage is 100%, so there is no parameter meaning for the description to add; the baseline for a parameterless tool applies.

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 names the resource ('delivery addresses') and scopes it to checkout, which hints it differs from the broader my_addresses sibling, but it is a noun phrase with no verb and never states plainly that it lists/returns addresses rather than, say, validating one. An agent can guess the purpose but must infer the operation.

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?

'Requires login' is the only guidance and it is a prerequisite, not a usage rule. Nothing says when to call this instead of my_addresses, my_address, or delivery_info, even though those siblings plausibly overlap on address data.

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