list_customer_addresses

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions it's a read-only tier operation via the tier label, which is helpful, but it doesn't describe pagination, ordering, whether deleted addresses are included, or what fields are returned. The tier label is partial credit but insufficient.

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: one stating purpose and one mapping to the REST endpoint plus tier. Zero wasted words, well front-loaded with the action and resource.

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 simple 1-param resource-listing tool with no output schema and no annotations, the description lacks pagination/ordering behavior and return format. It's adequate but leaves several practical questions unanswered that an agent might need (e.g., how many results, ordering, whether customer must exist).

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?

Only one parameter (customer_id) exists and the description's 'for a customer' implies its role. However, the description doesn't explain the format of customer_id (UUID, numeric ID, etc.) or clarify whether it matches other customer_listing tools. With 0% schema description coverage, the description should add more detail than it does; it names the parameter's role but not its format.

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?

Clear verb+resource+scope: 'List all service addresses for a customer.' The purpose is specific and unambiguous. It maps to a REST endpoint which adds concrete grounding, though it doesn't differentiate from get_customer_address beyond the plural/singular distinction.

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 tells us it lists all addresses for a customer but offers no guidance on when to use this versus get_customer_address, or when one would prefer this over get_customer. The tier label '[tier: readonly-owner]' hints at permissions but isn't actionable guidance.

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