Get debugger call stack

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

No annotations are provided, so the description carries the full burden. It discloses that the call stack is 'most recently captured' but does not reveal what happens if no pause has occurred, whether the operation is read-only, or what the return structure looks like. This is a significant gap for a debugger tool.

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, focused sentence that is front-loaded with the core action. It is appropriately concise, though it sacrifices useful detail for brevity.

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?

With no output schema and no annotations, the description must clarify the tool's behavior and return value. It only states the return type (call stack) and the source (recent pause) but omits important context like error conditions, session prerequisites, and what 'Raw session' means. This is insufficient for a tool with two parameters.

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 0%, yet the description provides no explanation of 'sessionId' or 'targetSessionId'. The term 'Raw session' is not tied to any parameter intention. The description adds no value beyond the schema properties themselves.

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 verb ('Return') and the resource ('most recently captured Debugger.paused call stack'), with a specific scope ('for a Raw session'). This distinguishes it from broader tools like debugger_get_paused_state, though it does not explicitly name alternatives.

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?

No guidance is given about when to use this tool versus alternatives. The phrase 'most recently captured' implies a prerequisite (a prior pause event), but it does not state that prerequisite explicitly or mention any conditions for valid usage.

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