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

The description adds context beyond the readOnlyHint annotation by stating 'including verification details', which is a behavioral trait. However, it does not disclose potential errors, rate limits, or authentication requirements. The annotation already declares read-only, so the description's additional detail is adequate but not extensive.

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 extremely concise with one sentence plus an API endpoint reference. Every word serves a purpose, and there is no fluff. It is front-loaded with the key action.

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 simplicity (one parameter, no output schema, readOnlyHint annotation), the description covers the essential information: what it does, input parameter, and API endpoint. It could mention the return format (single address object) but that is implicit. Overall complete for this context.

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 coverage is 100% with one parameter 'id' described as 'Address id, e.g. adr_...'. The description adds minimal value by saying 'by id', which is already implied. The baseline is 3 due to high schema coverage, and the description does not significantly enhance parameter understanding.

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 ('retrieve a single address by id'), the specific resource (address), and adds that it includes verification details. This distinguishes it from sibling tools like 'easypost_list_addresses' (multiple addresses) and 'easypost_verify_address' (verification only).

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 a single address by ID, but does not explicitly state when to use this tool versus alternatives (e.g., for verification, use 'verify_address'; for listing, use 'list_addresses'). No exclusions or prerequisites are mentioned.

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