cancel_interview

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

Without annotations, the description must disclose behavioral traits. It reveals the preview behavior (read-only by default), which is critical for an agent. However, it does not disclose other important aspects like whether the cancellation is reversible, permissions required, or notifications triggered. The partial disclosure earns a 3.

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 very short, with only 11 words. It is front-loaded and contains no unnecessary text. However, the brevity trades off clarity, particularly in explaining 'previews' and parameter roles.

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?

Given the complexity of a cancellation operation (no output schema, no annotations, missing parameter details), the description is incomplete. It does not clarify what 'previews' means exactly (e.g., what output is returned?), the impact of cancellation, or error conditions. More context is needed for an agent to use it correctly.

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?

With 0% schema description coverage, the description must compensate by explaining parameter meanings. It hints at the 'confirm' parameter role ('unless confirm=true'), but does not explain 'interview_id' or 'reason'. The description adds minimal value beyond the schema itself.

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 'Cancel an interview.' The verb 'Cancel' and resource 'interview' are specific. The phrase 'Previews unless confirm=true' hints at a preview mode, but the primary action is clear. It is distinct from sibling tools like schedule_interview or reschedule_interview.

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 some usage guidance: 'Previews unless confirm=true and writes are enabled.' This implies that by default it is a preview, and actual cancellation requires confirm=true and writes enabled. However, it does not explicitly state when to use this tool versus alternatives (e.g., rescheduling), nor does it mention any prerequisites or side effects.

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