scrapeer_cancel_run

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description doesn't need to repeat safety basics. It adds context about valid target state (running only, not completed/failed) and suggests aborting after timeout. This goes beyond the annotations without contradiction, though it doesn't detail post-cancel behavior (e.g., status becomes canceled).

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 compact and front-loaded with the core action. The 'USE THIS TOOL WHEN' and 'DO NOT USE' sections are clear, each sentence adds value, and the length is appropriate for a single-purpose cancellation tool.

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 one-parameter cancel tool with strong annotations and no output schema, the description covers the essential context: what the tool does, when to use it, and when to avoid it. The parameter source is specified, and no additional return-value documentation is necessary.

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 coverage is 100%: the single parameter execution_id is clearly described as the ID returned by scrapeer_run_flow or scrapeer_run_flow_and_wait. The tool description adds no additional parameter-specific semantics, but the schema already fully documents it, so baseline 3 applies.

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 starts with 'Cancel a running cloud execution,' which is a specific verb (cancel) plus resource (running cloud execution), clearly distinguishing it from sibling tools like run, list, get status, etc. It further narrows scope by explicitly excluding completed or failed runs.

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?

Provides explicit 'USE THIS TOOL WHEN' scenarios (run taking too long, user wants to stop, timeout from scrapeer_run_flow_and_wait) and a 'DO NOT USE' exclusion for completed/failed runs. This gives the agent clear decision criteria and directs to alternatives implicitly.

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