quick_evaluate

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

Describes atomic pause-eval-resume with ~5ms pause. Annotations already indicate idempotent and not read-only, and description adds detail without contradiction.

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?

Efficiently structured: concise summary, key details, usage note, and args. Each sentence adds value.

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 purpose, usage, parameters, and behavioral details. Minor gap: no mention of return value format, but acceptable given standard debugger behavior.

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 has no descriptions (0% coverage), but description provides clear parameter explanations with examples for expression and context for frame_id.

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?

Clearly states the tool evaluates an expression while the program is running via atomic pause-eval-resume. Distinguishes from sibling 'evaluate_expression' for stopped programs.

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?

Explicitly states when to use (program running) and when not to (stopped: use evaluate_expression). Also provides escape hatch reference.

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