AmdpDebugStep

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the stopped-debuggee precondition and the outside-batch-mode constraint, but it does not explain side effects on debug state, error behavior, or whether the call blocks waiting for a stop.

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 front-loaded sentence with compact tags; every clause adds either purpose or a usage constraint. There is no redundant or filler text.

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 schema is rich and the description adds the key precondition that the debuggee must be stopped and that the tool runs outside batch mode. With no output schema, the remaining gap around return values and blocked-call behavior is minor but real.

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 the schema already documents all three parameters clearly. The description only restates the action semantics at a high level and adds no syntax, defaults, or constraints beyond what the schema provides.

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 states a specific verb and resource: stepping a stopped AMDP debuggee. It also distinguishes the two step semantics (over a statement vs. to the next stop), which separates it from related siblings such as AmdpDebugWait or generic DebugStep.

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?

It gives clear context for use: the debuggee must be stopped, and the tool runs outside batch mode. However, it does not name explicit alternatives or say when another AMDP debug tool should be preferred.

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