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

Annotations only declare readOnly=false, openWorld=true, destructive=false. The description adds genuinely non-obvious behavior: the call spends credits, voicemail is left by default, and the agent will escalate to the user's own phone only for payment or decision steps. It stops short of stating cost magnitude, failure handling, or timing for the open-world call.

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?

Four tight sentences, front-loaded with the core action before the escalation caveat, then the `ask` instruction, then cost and voicemail defaults. Only 'your person' is slightly vague phrasing; nothing is redundant.

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 an open-world, credit-spending outbound-call tool with no output schema and no annotations beyond safety hints, the description covers what it does, what it needs, what it costs, and how it behaves on voicemail and escalation. Remaining gaps (how results are reported, what happens when the other side refuses) are moderate but not blocking.

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 80%, so the baseline is 3, but the description earns extra: it enumerates the kinds of detail that must go into `ask` (names, date, time, party size, account) and its escalation sentence gives implicit meaning to the `callback` parameter that the schema's terse 'crew_line (default), me, or a number' does not.

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 gives a concrete verb+resource: the agent places a phone call and does the asking itself, with named task types (reservation, appointment, question, cancellation). It is clear what the tool accomplishes, but it never explicitly names or distinguishes itself from the sibling `call` tool, leaving the boundary to inference.

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 context is implied through the example task list and the escalation rule (only rings your person when a card or decision is needed). However, there is no explicit when-not guidance and no mention of when to prefer `call`, `tell_me`, or `transcript` instead, so routing between siblings still requires guesswork.

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