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

With annotations already indicating readOnlyHint=true and destructiveHint=false, the description adds useful behavioral context by revealing the exact data returned (transcript, config snapshot, timestamps) and timestamp format. It does not contradict annotations and provides more behavior than just declaring it a read operation.

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?

One sentence delivers the action, the param source, and the important return fields. Everything earns its place and key info is front-loaded.

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 a single param, an existing output schema, and annotations covering safety, the description is nearly complete. It lacks explicit error behavior, but this is low-friction for a getter and the provided context plus schema are enough 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 schema only defines callId as a string with no description, and schema description coverage is 0%. The description compensates by specifying that callId is 'an ID returned by list_calls', giving the param provenance and expected form beyond the raw schema.

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 states a specific verb and resource ('Get one call'), names the direct source for the ID (list_calls), and lists the distinctive returned data (transcript, frozen assistantConfigSnapshot, ISO 8601 timestamps). This clearly distinguishes it from sibling tools like list_calls and other get_* tools.

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 description gives clear context by tying the callId to 'ID returned by list_calls', implying a workflow. It does not explicitly say when not to use it or contrast it with list_calls, so it lacks explicit exclusions, but a reader understands the intended usage.

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