Frame Snapshot

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, indicating a safe, read-only operation. The description adds little beyond confirming it returns a snapshot; it does not disclose what 'bounded' means, whether it waits for the frame to load, or other behavioral traits.

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 a single sentence, making it highly concise and front-loaded with the tool's primary purpose. However, it may be too terse, omitting important details that could aid understanding without adding length.

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?

The tool has 6 parameters and an output schema (not shown), so the description need not explain return values. However, it lacks context on how to select a frame (e.g., using frame_index or frame_selector) and what the 'bounded page outline' constitutes, which is partially addressed by the schema but not fully complete.

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?

With 33% schema description coverage, only frame_index and frame_selector have descriptions in the schema. The tool description does not add meaning for the other parameters (timeout, include_html, max_elements, max_text_chars) beyond their defaults and titles. This leaves the agent with limited understanding of their semantics.

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 returns a 'bounded page outline' from a selected iframe/frame, indicating it produces a structured representation of a frame's content. However, it does not distinguish this from sibling tools like frame_list or frame_find, which might also return frame information.

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?

The description provides no guidance on when to use this tool versus alternatives such as frame_list or frame_find. It does not mention prerequisites (e.g., a page must be loaded) or conditions under which the tool is appropriate.

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