aircall_resume_recording

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

Annotations already declare readOnlyHint=false and destructiveHint=false, indicating a non-read-only mutation. The description adds the prerequisite that the call must be active and recording paused, but doesn't disclose behavior when conditions aren't met or any side effects. Given the annotations, this is minimal but acceptable additional context.

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?

A single sentence that is direct and front-loaded with the action. Every word earns its place, with no filler or unnecessary elaboration.

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 a simple one-parameter tool with no output schema and good annotations, the description fully conveys the purpose and condition. The sibling context and the tool's simplicity mean no additional information is needed.

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 input schema has 100% coverage with call_id described as 'The call ID.' The description does not add any extra semantic detail beyond the schema, so the baseline score of 3 is appropriate.

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 the specific verb 'Resume' with the resource 'recording' and clearly states the scope 'on an active call after it was paused.' This distinguishes it from sibling tools like aircall_pause_recording and aircall_delete_recording, making the purpose unambiguous.

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 states the precondition 'after it was paused' and the target 'active call,' giving clear context for when to use the tool. While it doesn't explicitly name alternatives, the sibling list includes aircall_pause_recording, making the relationship obvious. It lacks explicit exclusion scenarios but the usage context is sufficient.

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