select_address

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It does not explain side effects, what happens on invalid index, or the output format. The description is too minimal for a state-changing tool.

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 a single concise sentence that front-loads the core information. It could benefit from additional details about the parameter, but it is not verbose.

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?

Given the tool has one parameter and an output schema, the description lacks completeness. It does not mention the output or tie the tool to the address retrieval process (e.g., using 'get_addresses' first). The context of the checkout flow is only hinted.

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 schema coverage is 0%, so the description must compensate. It only says 'by its index' without clarifying the index's semantics (e.g., 0-based or 1-based, valid range, or relationship to addresses from 'get_addresses'). This is insufficient.

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 action ('Select'), the resource ('delivery address'), and the method ('by its index'). It also specifies the context ('only use this BEFORE checkout'), distinguishing it from sibling tools like 'get_addresses' and 'checkout'.

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 description explicitly states when to use the tool ('Only use this BEFORE checkout'), which provides clear usage context. However, it does not mention when not to use it or explicitly name alternatives, though the constraint is clear.

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