cancel_elicitation_request

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Cancel' implies a mutation operation, it doesn't specify whether this is reversible, what permissions are required, what happens to associated resources, or what the response looks like. The description lacks critical behavioral context for a destructive operation.

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, efficient sentence with zero wasted words. It's appropriately sized for a simple operation and front-loads the essential information immediately.

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 mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what 'cancel' means operationally, what state changes occur, whether there are side effects, or what confirmation/response to expect. Given the complexity of cancellation operations and lack of structured documentation, more context 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?

Schema description coverage is 0%, but the description doesn't add any parameter information beyond what's obvious from the tool name. The single parameter 'request_id' is self-explanatory, but the description doesn't clarify format requirements, where to obtain valid IDs, or relationship to 'list_elicitation_requests' and 'get_elicitation_request' sibling tools.

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 target ('a pending elicitation request'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'cancel_task' or 'abort_workflow', which could handle similar cancellation operations on different resource types.

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 doesn't mention prerequisites (e.g., the request must be pending), exclusions (e.g., cannot cancel completed requests), or when to choose sibling tools like 'cancel_task' for different cancellation scenarios.

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