AmdpDebugCancel

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

No annotations are supplied, so the description carries the full burden; it does disclose two useful traits: the safety posture ('[read-only]') and the batch-mode restriction. It stops short of stating what happens to the debuggee after cancellation, what state_handle becomes, or what is returned.

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 bracketed tags plus a single sentence, with the action and its constraint front-loaded. Nothing is wasted and nothing needed is buried.

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?

With no output schema and no annotations, the definition covers the action and the batch-mode limitation but leaves the post-cancellation state and any return value unexplained. Adequate for a simple two-parameter debug helper, but thin for a tool that alters a live debugging session.

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 both parameters carry their own descriptions, including the full enum semantics for 'detail', so the schema does the documentation work. The description adds no param-level meaning beyond that, which is the baseline case.

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 (cancels) and resource (the stopped AMDP debuggee's execution), which is enough to distinguish it from AmdpDebugStart and AmdpDebugStep. It does not explicitly contrast with the close sibling AmdpDebugStop, so the boundary between 'cancel' and 'stop' must be inferred.

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?

Makes the precondition explicit (the debuggee must already be stopped) and adds a clear exclusion with 'Runs outside batch mode', which tells the agent not to wrap it in BatchBegin/BatchEnd. No named alternative for related debug flows, but context is clear.

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