evaluate_at_frame

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

No annotations provided, so burden falls on description. It explains paused requirement and scope access but does not mention whether evaluation is read-only or can cause side effects, nor any destructive potential.

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 concise sentences, front-loaded with purpose, no redundant information.

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?

For a debug tool with no output schema, description is fairly complete. Lacks details on error behavior or return format but adequate for use.

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 description adds value for frameIndex: '0 = top frame' and instructs to use get_debugger_state. Expression parameter has no extra detail beyond 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?

Clearly states the verb 'evaluate' and resource 'JavaScript expression in the scope of a paused call frame'. Explicitly distinguishes from sibling 'evaluate_js' by mentioning access to local variables, closure variables, and 'this'.

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?

Specifies condition 'Only works when execution is paused', and references 'use get_debugger_state to find available frames' for frameIndex. Contrasts with evaluate_js for scope.

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