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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description's 'cancel' is consistent with these. However, the description adds no further context about the effect on the execution (e.g., whether it's asynchronous, reversible, or what happens to related resources). Given the annotations cover the safety profile, the description is adequate but minimal.

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?

A single, concise sentence with no filler. The verb 'Cancel' is front-loaded, and the resource is specified clearly. Every word earns its place.

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 cancel operation with two fully described parameters and annotations covering idempotency and destructiveness, the description is sufficient for an agent to know what to do. There is no output schema, so return values aren't expected. A minor gap is that it doesn't mention potential failure modes (e.g., canceling an already-completed execution), but that's not critical.

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 input schema provides clear descriptions for both parameters (connector_id and execution_id) with 100% coverage. The description adds no additional parameter information, so it relies entirely on the schema. Baseline of 3 is appropriate when the schema fully documents parameters.

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 'Cancel a running connector execution' states a specific verb (cancel) and resource (connector execution), clearly distinguishing it from sibling tools like connector_run and connector_status. The action is unambiguous and instantly understood.

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 on when to use this tool versus alternatives. It doesn't mention that it should be used to stop an execution that is no longer needed, nor does it reference any sibling tools or conditions for cancellation. An agent would have to infer the context from the tool name alone.

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