execution.stop

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. 'Stop the current workflow execution' implies a destructive/mutating operation, but doesn't specify whether this is reversible, what happens to in-progress work, whether confirmation is needed, or what the expected outcome looks like. For a potentially destructive tool with zero annotation coverage, this is inadequate.

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 that communicates the core functionality without any wasted words. It's front-loaded with the essential information and achieves maximum clarity with minimal verbiage.

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 potentially destructive execution control tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'stop' means operationally, what state the workflow enters after stopping, whether data is preserved, or what happens if there's no current execution. The context demands more behavioral detail than provided.

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 tool has zero parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't mention parameters since none exist, which is correct. A baseline of 4 is appropriate for zero-parameter tools when the schema coverage is complete.

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 ('Stop') and the target ('the current workflow execution'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from potential alternatives like 'execution.getStatus' or 'workflow.undo' that might also affect execution state, which prevents a perfect score.

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 about when to use this tool versus alternatives. With sibling tools like 'execution.start', 'execution.getStatus', and various workflow control tools (undo/redo), there's no indication of appropriate contexts, prerequisites, or exclusions for using this stop function.

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