DebugSetStackPosition

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

With no structured annotations, the description carries the burden and does well: it declares read-only behavior, the required debuggee state, and that it is unsupported in batch mode. It omits where state_handle comes from and what the call returns, leaving a small gap.

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?

One dense sentence with tag prefixes, front-loaded with the action. Every clause carries information, though the semicolon-chained phrasing is slightly dense rather than ideally structured.

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 three-parameter debug tool with no output schema, the description covers precondition, mode restriction, and the non-stepping semantics. The main missing piece is how the state_handle is obtained (presumably from DebugGetStack).

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%, so all three parameters are documented in the schema itself, including the 'position' ordering rule and 'detail' verbosity enum. The description adds no parameter-level meaning beyond the schema, so baseline 3 applies.

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?

Names a specific verb and resource ('Selects the stack frame variables are read in') and adds the key nuance that execution does not advance, which separates it from DebugStep. It does not name a sibling explicitly, but the operation is unambiguous.

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?

'Needs a stopped debuggee' and 'Runs outside batch mode' give explicit preconditions and an exclusion. It stops short of routing to alternatives (e.g., use DebugGetStack to list frames first), so not a 5.

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