cancelBulkCall

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

Annotations already declare destructiveHint=true, so the destructiveness is known. However, the description adds no additional behavioral context, such as whether cancellation is irreversible, what happens to ongoing calls, or if any confirmation is needed. It simply restates the purpose without disclosing side effects beyond what annotations already indicate.

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, direct sentence followed by a tag. It is extremely concise, front-loaded, and contains no wasted words. Every part earns its place, making it easily scannable.

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 cancellation tool with one parameter and annotations, the description is adequate but not thorough. It omits behavioral nuances like what happens to already-placed calls or whether cancellation is reversible. Given the destructive nature (annotations), some additional context would improve completeness, but the tool's simplicity keeps this from being a failing score.

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 schema has 100% coverage, with bulk_call_id described as 'Id of the bulk call campaign.' The description adds no extra meaning beyond the schema, so the baseline score of 3 is appropriate. No additional parameter context is needed for this simple one-param tool.

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 action "Cancel" and the resource "bulk-call campaign," which is specific and distinguishes it from sibling tools like createBulkCall, getBulkCall, or bulkCallActions. The purpose is immediately obvious.

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 no guidance on when to use this tool versus alternatives. It does not mention conditions for cancellation, prerequisites, or contrast with similar tools like bulkCallActions, which might also modify campaign state. The intended use case is only implied by the verb 'cancel.'

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