pilot_frames

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

Describes exactly what the tool returns (numbered list with index, type, URL, active frame arrow) and what happens when no iframes exist. States 'Errors: None', so the user knows it's safe. Even without annotations, the description fully discloses 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?

The description is very concise, with each sentence adding value. It is front-loaded with the main purpose, then usage guidance, then returns. No extraneous text.

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 tool with zero parameters and no output schema, the description fully explains the return format and edge cases. No additional information is needed.

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, and schema coverage is 100%. Per rules, baseline is 4. The description adds no parameter detail because none are needed.

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 that the tool lists all frames on the current page with indices, names, and URLs. It distinguishes itself from sibling tools like pilot_frame_select by explicitly mentioning that tool for switching contexts.

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?

Provides explicit when-to-use scenarios: to see existing iframes, find one to interact with, or verify page structure before switching. Also tells the user to use pilot_frame_select to switch, giving clear alternatives.

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