GetCustomersMeAddressesAddress_id

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates this is a read operation ('Retrieve'), but lacks details on authentication requirements (e.g., logged-in customer context), error handling, rate limits, or response format. The mention of expanding relations and selecting fields hints at behavioral traits, but is vague and incomplete.

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 with two sentences that are front-loaded with the core purpose. There's no wasted text, though it could be slightly more structured by separating usage guidance from parameter hints.

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 2 parameters with 0% schema coverage, no annotations, and no output schema, the description is incomplete. It lacks details on authentication, error cases, response structure, and clear parameter semantics, making it inadequate for safe and effective use by an AI agent.

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 description must compensate for undocumented parameters. It mentions 'expand the address's relations' and 'select the fields that should be returned', which loosely relates to the 'fields' parameter, but doesn't explain the 'address_id' parameter or provide specific syntax, formats, or examples for either. This adds minimal value beyond the bare schema.

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 ('an address of the logged-in customer'), making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from its sibling 'GetCustomersMeAddresses', which likely retrieves all addresses rather than a specific one by ID.

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 provides no guidance on when to use this tool versus alternatives like 'GetCustomersMeAddresses' for listing addresses or other customer-related tools. It mentions expanding relations or selecting fields, but this is about usage parameters, not contextual decision-making.

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