aircall_unarchive_call

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

Annotations indicate readOnlyHint=false and destructiveHint=false, aligning with the mutation implied by 'unarchive.' The description adds the specific behavioral outcome of restoring the call to the main list, which is useful context beyond the annotations.

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?

The description is a single, concise sentence that clearly states the purpose and effect without any extraneous information. It is front-loaded with the primary verb and resource.

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, the description covers the core functionality and effect. However, it does not mention error conditions (e.g., call not found or already unarchived) or what the response contains, which would be marginally useful but not essential given the tool's simplicity.

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 for call_id, but the parameter description in the schema incorrectly states 'The call ID to archive' instead of 'unarchive.' This is a copy-paste error and misleading for the tool's purpose. The description does not correct or add parameter meaning, so it fails to compensate for the schema's inaccuracy.

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's action: 'Unarchive a previously archived call, restoring it to the main call list.' This uses a specific verb and resource, and distinguishes it from the sibling tool aircall_archive_call by indicating the reverse operation.

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 provides clear context: use when a call is archived and needs to be restored to the main list. It does not explicitly mention alternatives or when not to use, but the context is sufficient for typical usage.

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