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

With no annotations, the description carries the full burden and does disclose the key traits: it blocks, default 45 s, capped at 50 s, then degrades to a message back to the task. It does not mention permissions or failure behavior if the user declines, which keeps it short of a 5.

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?

Three sentences, front-loaded with the core action and capped by the async fallback. Dense but every clause carries information; no filler.

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?

No output schema and no annotations, so the description must explain the return value, and it does ('Returns a link to the picture'). Combined with the timeout and fallback explanation, an agent has enough to call it correctly; only the 'why' parameter remains unexplained.

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 33%. The description adds real meaning for two of three params ('give from' ties the callback to the task; 'wait_seconds, up to 50' gives the cap and default). The required 'why' parameter is never explained, leaving a gap that neither schema nor description fills.

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?

States a specific verb and resource ('Ask the user to take a photo with their iPhone') plus the concrete use cases (whiteboard, receipt, document). It is clearly distinguishable from phone_ask and phone_result, which it names directly.

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?

Tells the agent when to reach for this tool and points at the async fallback path ('give from', or phone_result) when the user answers later. It stops short of explicit when-not conditions, but the scenario is unambiguous.

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