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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, covering the safety profile. The description adds value by clarifying consequences: finished attempts keep results and no further charges or queuing occur. It does not explain idempotency behavior despite the non-idempotent annotation.

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?

Two short sentences, front-loaded with the action and scoped effects. Every clause adds information with no redundancy.

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?

The description covers behavioral consequences well and annotations carry the destructive profile, but the sparse schema (33% coverage) leaves required parameters undocumented and the description does not compensate. For a 3-param destructive mutation tool, this is a noticeable gap.

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 only 33% – only organization_id has a description. The description mentions no parameter names or meanings, leaving agent_id and run_id with no semantic guidance beyond the schema's required list and string types.

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 'Cancel' with the resource 'simulation run' and scope ('queued or running'). It distinguishes from siblings such as start_simulation_run and get_simulation_run by verb, so an agent can select it correctly without opening the schema.

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?

Gives the core use case ('queued or running') but no explicit when-not conditions or alternatives. It doesn't mention when to prefer get_simulation_run or that already-finished runs cannot be cancelled, leaving routing implicit.

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