Cancel Runtime Work

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

No annotations exist, so description is the sole source. It correctly notes 'best-effort' and 'daemon reset', implying possible side effects and partial success. However, it omits details on what exactly gets reset or how errors are communicated.

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 concise sentences, no filler. First sentence states core purpose, second provides behavioral guidance. Perfectly front-loaded.

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?

Given the tool's simplicity (0 required params, output schema exists), description sufficiently covers purpose and a key usage constraint. Could be more complete by noting expected result or failure modes, but output schema mitigates need for return value details.

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% and description adds no extra meaning to 'reason' parameter beyond what schema already states. Baseline score of 3 is appropriate.

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?

Clearly states the tool does 'cancellation and daemon reset for long-running MCP browser work'. The verb 'cancel' and resource 'runtime work' are specific. Distinguishes from sibling tools which are focused on UI interaction or data operations.

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 advises preferring 'notifications/cancelled' over this tool for in-flight requests. Provides context for when alternative method is more appropriate, though does not exhaustively list other alternatives.

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