athena_cancel

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'in-flight' and 'server-side' but does not describe side effects, whether cancellation is idempotent, what happens if the execution is already finished, or any permission requirements. This is a minimal behavioral disclosure for a mutating 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 extremely concise: one clear action sentence plus an Args block for the single parameter. Every sentence earns its place and the main purpose is front-loaded.

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 single-parameter cancellation tool with an output schema present, the description provides enough to select and invoke it. The main gaps are behavioral details like error handling and idempotency, but the operation and parameter are clearly specified.

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 0% description coverage, but the description does clarify that execution_id is 'The Athena execution id', adding slight meaning over the schema title 'Execution Id'. It does not mention format, source, or relationship to other tools like athena_run_query, so the compensation is adequate but minimal.

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 states a specific verb ('Cancel') and target resource ('in-flight Athena execution'), and clarifies the server-side API call (StopQueryExecution). This clearly distinguishes it from sibling tools like athena_run_query and athena_get_execution_status.

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?

'Cancel an in-flight Athena execution' gives clear context for when this tool applies, and the 'in-flight' qualifier implies it is not for completed or failed queries. It does not explicitly name alternatives or state when not to use it, but the condition is clear enough for this unique operation.

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