debug_eval

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

No annotations provided, so the description carries the full burden. It mentions evaluation 'at the current pause' but does not disclose potential side effects of expressions (e.g., assignments) or error conditions like invalid syntax or un-paused session. Minimal but adequate for basic behavior.

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?

Three sentences, each purposeful: purpose, prerequisite, examples. Front-loaded and efficient with no wasted words.

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, prerequisite, and input style. Lacks description of output format (e.g., return value type) and error behavior. Given no output schema and moderate complexity, it is mostly complete but could be enhanced.

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% with each parameter described, but the description adds value by giving example expressions and noting that frame_id is optional. The prerequisite of paused session provides context for device_id. Adds meaning 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?

The description clearly states the tool evaluates Swift/ObjC expressions during a debug pause, with examples showing typical usage. It distinguishes from sibling tools like debug_step (stepping) and debug_state (viewing state).

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 the prerequisite 'Session must be paused,' which is crucial for correct usage. Provides concrete examples of expressions, guiding the agent on what inputs are appropriate. No mention of alternatives, but the prerequisite is strong.

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