my_address

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

No annotations are provided, so the description carries the full burden, and it does disclose the authentication requirement, which is genuinely useful. However, it says nothing about whether this is a read-only lookup, what happens with an unknown or other user's address_id, or any permission scoping beyond login.

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 short, front-loaded sentences with no filler. The brevity is appropriate in form but leaves the definition under-specified rather than over-written.

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?

An output schema exists, so return values need not be explained, and the tool is structurally simple with one required parameter. Still, the missing parameter meaning and lack of annotation coverage for a login-gated resource lookup leave a real gap.

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% and the single parameter address_id has no title beyond its name, yet the description never mentions it or its expected format. The one parameter that determines the call's success is left entirely 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 names a specific resource ("a single saved address"), which implicitly distinguishes it from the sibling my_addresses list tool. There is no explicit verb, but an agent can infer retrieval of one address by id without ambiguity.

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 only guidance is the precondition "Requires login"; there is no statement of when to use this versus my_addresses or address_search, nor any exclusion. An agent must infer the single-vs-list distinction from the name alone.

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