pilot_frame_reset

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

Discloses that all refs are cleared and that the tool always succeeds. With no annotations, this provides necessary behavioral context for a state-reset operation.

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?

Description is concise, front-loads purpose, then covers usage, side effects, and return value. Every sentence adds value without redundancy.

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 behavior, side effects (refs cleared), follow-up action, return value, and error behavior. No gaps for a simple tool with no parameters or output schema.

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?

No parameters exist, so the description correctly states that. Baseline score of 4 is appropriate as schema is empty and description does not need to add param details.

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 switches browser context back to the main page frame after working inside an iframe. Distinguishes from sibling pilot_frame_select by focusing on resetting context.

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 says when to use (after interacting with an iframe) and provides a follow-up action (run pilot_snapshot). Could be improved by stating when not to use, but context is sufficient.

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