saved_addresses

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

With no annotations supplied, the description carries the full burden. It does disclose a meaningful behavioral trait beyond the name — that results include private address details, a privacy-relevant fact — and that entries carry selection indexes. However, it says nothing about ordering, pagination, empty-state behavior, or whether an authenticated session is required to see private fields.

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?

One short sentence with no filler, and the core action ('List saved addresses') is front-loaded ahead of the qualifiers. Nothing is repeated from the schema or title.

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?

There is no output schema and no annotations, so the description is the only source of return-value information, and it only partially covers it. 'Selection indexes' is never explained (what the index refers to, and how to use it in a subsequent call), which is the key detail an agent would need to act on the result.

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, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly avoids restating an empty schema.

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 saved addresses') and adds two distinguishing attributes: selection indexes and private address details. That is enough to separate it from siblings like saved_address_count and suggest_address, though it never names those siblings 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?

The mention of 'selection indexes' implies the tool is meant to be called when the agent needs to pick an address for a later action, but this is left implicit. It gives no explicit guidance on when to use this versus saved_address_count (count only) or suggest_address (address lookup), so the agent must infer the routing.

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