firestarter_addresses

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds valuable behavioral details: values are masked (partial street, no zip/phone), the default address is marked, and addresses are referenced by id so full values are not needed. This contextualizes the read-only nature beyond what annotations provide.

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 front-loaded with the core action ('List the buyer's saved shipping addresses'), then adds supporting details about masking, defaults, and integration. While it is a bit longer than strictly necessary, each sentence contributes meaningful information, and the structure is logical.

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?

Without an output schema, the description is responsible for explaining return values. It covers the key aspects: masked addresses, default address marking, and the address_id field's role in downstream tools. It does not mention pagination or error scenarios, but for a simple list operation this is likely sufficient. The tool is simple enough that the description provides adequate context for an agent.

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 is no parameter documentation needed. The schema description coverage is 100% (trivially), and the description appropriately focuses on the output and integration rather than inputs, which is consistent with a no-arg listing tool.

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 states the verb 'List', the resource 'saved shipping addresses', and the masking attribute. It also explains the primary purpose of returning address_id for use in firestarter_execute and firestarter_approve, and implicitly distinguishes itself from sibling tools like firestarter_save_address and firestarter_shipping_options.

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?

It provides clear context for when to use the tool: to list saved addresses and obtain IDs for use in other workflows. The statement that 'a saved address never has to be re-typed' communicates a practical benefit. It does not explicitly state when not to use it, but the purpose is clear enough that an agent can infer its role relative to related tools.

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