resume

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

With no annotations, the description carries the full burden. It explains the key behavior ('ends the current pause'), adds a required follow-up action (remove temporary debugger statements), and tells the agent to relay the '_ui' field from the response. Minor gaps like failure behavior remain, but this is solid for a zero-parameter control tool.

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?

The description is three sentences and every sentence earns its place: purpose/timing, post-call cleanup, and user-facing response handling. It is front-loaded with the core action and contains no fluff.

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 low complexity, zero parameters, and lack of output schema, this description is sufficiently complete. It covers when to call it, what it does, what to do afterward, and what to relay from the response.

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 tool has zero parameters, so the baseline for parameter semantics is 4. The description needs no parameter-level guidance, and it appropriately adds no irrelevant parameter information.

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 opens with a specific verb and resource: 'Resume script execution' and immediately clarifies it 'ends the current pause.' This distinguishes it from sibling stepping commands and clearly identifies the tool's role in the debugging session.

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 says to use resume 'after collecting all needed variable data,' providing a clear usage condition. It does not explicitly exclude alternatives like stepInto/stepOut, but the sequencing context is strong enough for an agent to know when resume is appropriate.

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