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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds meaningful context beyond those annotations by specifying exactly what is read, that it is scoped to one call ID, and that only masked/status metadata is returned.

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?

Two sentences, front-loaded with the action and scope, and every clause adds information. There is no filler or repetition of schema details.

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 annotations covering the safety profile and an output schema present, the description covers the essential input scope and return limitation. The main remaining gap is the undocumented optional tenant_id parameter, but overall the description is sufficient for a simple read-only status tool.

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 description coverage is 0%, so the description must compensate, but it only references the call ID concept instead of the parameter name or the optional tenant_id. call_id is inferable from 'AI Receptionist call ID', but tenant_id gets no explanation, leaving a clear semantic gap.

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 uses a specific verb ('Read') and precisely names the resources involved: the Desk ticket, CRM callback task, call-link receipt, and A2P-gated inbound SMS posture for a single AI Receptionist call ID. 'Returns masked/status metadata only' also differentiates this from broader or more detailed sibling 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 makes the usage context clear: use it when you need the status/masked metadata for one AI Receptionist call ID. It does not explicitly name alternatives, but the singular-call scope and 'status metadata only' limitation provide practical selection guidance.

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