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

Annotations already declare destructive=true, idempotent=true and openWorld=false, yet the description still adds real value: terminal-state no-op behavior, the fact that updated run details are returned, and a required x402 payment signature in _meta. The payment/auth prerequisite is exactly the kind of operational context the schema cannot convey.

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?

Well front-loaded: the core action and state constraint come first, followed by no-op conditions, usage, and payment prerequisites. The labeled USAGE/USAGE EXAMPLES blocks with 'user_input:' lines are slightly redundant padding, costing it the top mark.

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?

An output schema exists, so return values need no elaboration, and annotations cover the safety profile. Combined with the description's state preconditions and the x402 payment requirement, an agent has everything needed to call this correctly.

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 100%, so runId and gracefully are already fully documented, including the 30-second graceful timeout. The description's example ('Gracefully abort run y2h7sK3Wc') implies the flag but adds no syntax or format detail beyond the schema, so the 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?

States a specific verb (Abort) applied to a specific resource (Actor run) and narrows the scope to runs 'currently starting or running'. This is clearly distinguishable from the read-oriented siblings like get-actor-run and get-dataset-items.

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?

Explicitly states when to reach for it ('stop a run that is taking too long or misconfigured') and when it is a no-op (runs already SUCCEEDED, FAILED, ABORTING, ABORTED, or TIMED-OUT). The when-not condition is unusually precise and prevents wasted calls.

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