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

With no annotations, the description carries the full behavioral burden, and it does disclose that lookups can be in a pending state. It says nothing about what is returned while pending (error vs partial result), whether results expire, id lifetime, or rate limits on repeated polling — material gaps for an unannotated retrieval tool.

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?

A single tight sentence with the action front-loaded and the qualifying condition in parentheses. No filler, though the parenthetical could be promoted to a proper clause for scannability.

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?

There is no output schema, no annotations, and no parameter documentation, so the description must explain the return shape and the pending-result lifecycle on its own — and it does neither. For an async-result retrieval tool an agent needs to know what 'pending' yields and how to obtain the id.

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 0%, so the schema only says 'id: string'. The description clarifies that the id refers to an earlier lookup, but not where that id comes from, its format, or what happens with an unknown/expired id, which is the key semantic gap for a single-parameter tool.

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 verb ('Fetch') and resource ('the result of an earlier lookup'), and scopes it to a lookup identified by id. It is distinguishable from the sibling enrich_* and search_* tools, though it never names the tool that actually creates the lookup being fetched.

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?

It gives one concrete usage condition — 'use it when a person lookup is still pending' — which implies a polling pattern. It does not explain when not to call it, what to do once the lookup completes, or which sibling initiates the lookup, so the guidance is partial rather than complete.

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