pyocd_target_step_out

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

No annotations provided; the description carries the full burden. It explains the internal steps: sets temporary breakpoint at LR, resumes, waits for hit, cleans up, and returns new position. However, it fails to describe behavior on timeout (e.g., error, return, or exception).

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, front-loaded with the purpose, and each sentence adds value. It is concise but could be slightly more streamlined.

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 (1 param, output schema exists), the description covers the main flow and return value. However, missing timeout behavior and error handling slightly reduce completeness.

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 description coverage is 100% (timeout parameter fully described in schema). The description adds no extra meaning beyond the schema, only indirectly referencing the wait. Baseline 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?

The description clearly states the action: 'Execute until the current function returns (step out)'. It distinguishes from sibling tools like pyocd_target_step by specifying the step-out behavior and mechanism.

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 to return from a function) but does not explicitly state when to use versus alternatives like pyocd_target_step or pyocd_target_resume. No 'when not to use' or alternative names are provided.

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