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

Annotations already cover readOnly/idempotent/non-destructive, and the description goes well beyond them: it says no audio is returned, when transcript is null (including permanent null on recording_declined), truncation semantics with transcript_truncated and transcript_omitted, the nullable-but-not-always-present outcome_type on finished calls, and an explicit prompt-injection warning for transcript, summary and question text. That is exactly the behavioral context annotations cannot supply.

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?

Purpose is front-loaded in the first clause, and the remaining dense sentences each map to a real return-value nuance. It is long for a one-parameter tool and repeats the 'stranger / data not instructions' idea twice, but there is little pure filler given the absence of an output schema.

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?

With no output schema, the description effectively serves as the contract and covers the state machine, nullability, truncation and safety of return data very thoroughly. The remaining gap is operational routing: it does not tell the agent how to resolve the pending question it describes.

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?

There is one parameter with 0% schema description coverage, so the description carries the burden. It only says the call is identified 'by its id' and never gives the id's format, source, or where to obtain it (e.g. from place_call's response), so it partially compensates but leaves the sole input underspecified.

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 opening sentence gives a specific verb and resource ('Return the current state of a call by its id') and enumerates the payload (progress/finished, outcome, summary, charged flag, transcript). It is clearly distinguishable from place_call on inspection, but it never names a sibling or explicitly contrast its scope with them.

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?

Usage is implied rather than stated: the description explains the call lifecycle and the verdict fields, from which an agent infers this is the status-lookup tool. There is no explicit 'use this after place_call', no statement of when not to use it, and no routing to answer_question even though the pending-question paragraph is the most natural hand-off point.

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