Wait for Call Completion and Report Outcome

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

Discloses blocking behavior, terminal statuses, timeout handling, and that the tool can be called again if timed_out. Annotations (readOnlyHint=true, etc.) align with description; no contradictions.

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?

Extremely concise: main paragraph followed by Args and Returns sections. Front-loaded with key behavior, no waste.

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, so description correctly explains return JSON shape and timeout behavior. Could mention idempotency, but annotations handle that. Minor gap: no mention of error cases.

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?

Input schema has 100% description coverage, so baseline is 3. Description adds default values and context (e.g., 'seconds between polls') but does not significantly extend schema info.

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 clearly states the tool blocks until a call reaches terminal status or timeout, then returns outcome report. It distinguishes itself from siblings like elevenlabs_get_call_report by emphasizing it waits for completion.

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?

Explicitly recommends use as follow-up to elevenlabs_make_outbound_call, providing workflow clarity. Does not mention when not to use, but context is clear.

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