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

With no annotations, the description carries the full burden of behavioral disclosure. It hints that the tool returns an answer for a pending request, but says nothing about whether it blocks, errors if not ready, requires authentication, rate limits, or what the return value looks like. Only minimal behavioral context is provided.

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 a single concise sentence fragment, so it wastes no words. However, its structure is weak: it is not a complete sentence with a verb, and it front-loads a noun phrase rather than clearly stating the tool's action, making it less immediately parseable.

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?

For a tool with a required 'request' parameter, no output schema, and no annotations, the description is far too sparse. It does not explain the request identifier, how to obtain it, what the answer format is, or how to handle pending versus completed states, leaving critical context missing for correct invocation.

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?

The single parameter 'request' has 0% schema description coverage, and the description does not mention it at all. It gives no indication of what the request value should be, its expected format, or where to obtain it, so the description fails to compensate for the missing schema documentation.

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 identifies the tool as returning 'the answer' to specific sibling tools (phone_location, phone_ask, phone_photo) that were 'still waiting,' which gives a vague sense of purpose and some sibling differentiation. However, it lacks a clear action verb and does not explicitly state that this is a retrieval or polling tool for asynchronous phone requests.

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 mention of 'still waiting' implies the tool is used after a phone_* call returns a pending state, but there is no explicit instruction like 'use this when X' or 'do not use this for Y.' No alternatives or exclusions are named, leaving usage entirely inferential.

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