List Delivery Addresses

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well established. The description adds useful behavioral scope by specifying that it returns either the saved or currently selected address, and that it operates on the user's Lazada account context.

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, tightly written sentence with no filler. It front-loads the action ('read') and the object ('saved or currently selected delivery address'), making it immediately scannable and useful.

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 tool with robust annotations and an output schema, the description is complete. It tells the agent what resource is being accessed and the account scope, while the output schema handles return-value expectations.

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 and schema_description_coverage is 100%, so there is no parameter detail for the description to add. With no parameters, the baseline for this dimension is 4, and the description adequately conveys that the operation is context-dependent rather than argument-driven.

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 uses the specific verb 'read' and clearly identifies the resource: the user's saved or currently selected delivery address for their Lazada account. This distinguishes it well from sibling tools like list_delivery_slots, which concern delivery time slots rather than address data.

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 gives clear context: use this when you need to read the saved or currently selected delivery address. It does not explicitly name alternatives or exclusion conditions, but the use case is scoped enough for an agent to select it confidently.

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