firestarter_addresses

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

Annotations already declares readOnlyHint=true and destructiveHint=false, so the safe read nature is covered. The description adds useful behavioral context: values are masked (partial street, no zip/phone), the default address is marked, and a full address is not needed for referencing by id. This goes beyond the annotations and helps set expectations for the returned data.

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 two sentences that front-load the core action, then add workflow and data-format context. Every sentence contributes value with no fluff or repetition of the schema or annotations.

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-only list tool with no output schema, the description fully covers what the tool does, when to use it, what the output looks like (masked, default marked), and how to use the result (pass address_id). No critical gaps remain.

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 and the schema reflects that with 100% coverage, so there is no parameter description burden. The description still adds useful context about the returned address identifiers, which is more than necessary for parameter semantics.

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 opens with a specific verb and resource: 'List the buyer's saved shipping addresses (masked).' This clearly identifies the tool as a read-only listing operation and distinguishes it from sibling tools like firestarter_save_address (writing) and firestarter_shipping_options (shipping selection).

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 explicitly states when to use the tool: check for an existing address BEFORE asking the buyer to type one. It also tells the agent what to do next: pass the matching `address_id` to firestarter_execute or firestarter_approve. This provides clear workflow guidance and differentiates from the alternative of manually entering an address.

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