GetCustomersMeAddresses

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

No annotations are provided, so the description carries the full burden. It mentions filtering, sorting, and pagination, but lacks critical behavioral details: whether this is a read-only operation, what permissions are required, how errors are handled, or the response format. For a tool with 8 parameters and no annotation coverage, this is insufficient disclosure.

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 concise at three sentences, front-loading the core purpose. Each sentence adds value: retrieval, filtering capability, and sorting/pagination options. There's no redundant or wasted text, though it could be more structured for clarity.

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 complexity (8 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the return format, error conditions, authentication needs, or default behavior (e.g., what happens if no parameters are provided). For a retrieval tool with many options, more context is needed to use it effectively.

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?

Schema description coverage is 0%, so the schema provides no parameter documentation. The description mentions filtering by 'country_code' and hints at sorting/pagination, but only covers 1 of 8 parameters explicitly (country_code) and vaguely references others (order, offset, limit). It doesn't explain fields like 'q', 'city', or 'postal_code', leaving most parameters undocumented.

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 ('retrieve') and resource ('addresses of the logged-in customer'), making the purpose evident. It distinguishes this tool from siblings like GetCustomersMe (which retrieves customer info) and GetCustomersMeAddressesAddress_id (which retrieves a specific address). However, it doesn't specify whether this returns all addresses or a subset by default.

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 implies usage for retrieving addresses with optional filtering, sorting, or pagination, but doesn't explicitly state when to use this versus alternatives like GetCustomersMeAddressesAddress_id for a single address. No exclusions or prerequisites are mentioned, leaving some ambiguity about appropriate contexts.

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