debug_state

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

No annotations provided, so description carries full burden. Describes default and optional behavior but omits side effects, authentication, or confirmation that operation is non-destructive. Could explicitly state it does not modify 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?

Two sentences, front-loaded with primary purpose, no redundant words. Efficiently conveys default behavior and optional extensions.

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?

Covers default and optional outputs but does not detail the structure of 'state' or 'breakpoints' objects. Lacks mention of prerequisites (e.g., active debug session). For a read operation with no output schema, more detail on return types would improve 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 coverage is 100% but descriptions are brief. Tool description adds meaningful detail for each optional parameter (e.g., 'fetch the stack of the stopped thread', 'enumerate all threads'), providing context beyond the schema.

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?

Description clearly states verb 'Query', resource 'debug session', and default return values '{state, breakpoints}'. Distinguishes from sibling tools like debug_attach, debug_step, debug_eval.

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?

Explains when to use optional parameters (e.g., include_stack, include_vars) with concrete effects. Does not explicitly contrast with alternative tools or provide when-not-to-use guidance.

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