pin_step

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not state whether the call blocks until the step completes, whether the thread must already be halted, how other threads are affected, or what the result indicates — significant gaps for a tool that mutates execution state.

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?

A single compact sentence with the special-value convention appended in parentheses; no wasted words and the operation is 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?

For a one-parameter tool with no output schema, the description covers the parameter's semantics adequately but omits preconditions (paused state) and timing/blocking behavior. It is minimally sufficient but leaves real gaps an agent would care about before invoking.

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 the schema documents tid only as 'OS thread id'. The description adds genuine meaning by defining the special value tid 0 = last event thread, which the schema does not convey, so it exceeds the baseline 3.

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 ('single-step') and resource ('the given OS thread'), which is clearly distinct from sibling operations like pin_resume, pin_pause, and pin_stop. It does not explicitly name or contrast with those siblings, so it falls short of the 5 bar.

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?

Usage is implied by the noun phrase 'single-step' in a debugging context, and the tid=0 convention hints at the common no-argument case. However, it never says when to step versus resume/pause, nor whether a precondition (thread must be paused/halted) is required.

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