get_addresses

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

Description is straightforward about being a read operation (get list). No annotations provided, but no behavioral quirks need disclosure. However, it does not mention prerequisites like being logged in, which might be inferred from sibling tools.

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 sentences, first states purpose, second gives usage context. No wasted words.

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?

Complete enough for a simple getter with an output schema. Tells when to use and with which sibling. Could mention authentication but not critical given sibling tools include check_login.

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?

No parameters exist (schema coverage 100%), so description adds nothing beyond the schema. Baseline 4 is appropriate for zero-parameter tools.

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?

Clearly states 'Get the list of saved addresses' which is a specific verb+resource. Also differentiates from sibling tools like select_address and check_cart by mentioning their combined usage for changing an 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?

Explicitly tells when to use: 'Use this and select_address to change address on the cart page, if the address in check_cart is incorrect.' This provides a clear workflow context and alternatives.

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