step_out

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

The phrase 'wait for the next stop' adds a behavioral detail beyond the sparse annotations (openWorldHint=false, destructiveHint=false), indicating the command is asynchronous and pauses at the next stop. It does not mention potential breakpoint hits during step-out, but adds value beyond annotations.

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 a single, clear sentence with no redundant words. It is front-loaded with the action and provides the expected outcome efficiently.

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 tool is simple (0 params, clear action) and the description covers the essential behavior. It could mention edge cases like stepping out of the outermost frame, but given the availability of an output schema and the simple nature, it is sufficiently complete.

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?

With zero parameters, the schema carries no meaning. The description properly focuses on behavior, and the baseline for zero parameters is 4. No parameter information is needed.

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 'Step out of the current frame and wait for the next stop' clearly states the tool's action and scope. It distinguishes itself from sibling tools step_into and step_over by specifying 'out of the current frame'.

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 implies usage when a user wants to exit a function and return to the caller, but it does not explicitly state when to use it over alternatives. No when-to-use or exclusions are provided, though the sibling naming gives context.

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