Frame Snapshot

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds the 'bounded' qualifier, indicating output limits (e.g., max_elements, max_text_chars), which is not present in annotations. It also implies frame selection is required, adding context beyond structured fields.

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 with no filler, front-loaded with the action ('Return') and scope. Every word contributes meaning.

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?

Given the presence of an output schema and comprehensive annotations, the description adequately covers the core behavior. It could further clarify what 'page outline' means or how to select a frame, but the schema handles those details. It is complete enough for a tool with this complexity.

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 description coverage is only 33%, and the description does not compensate by explaining parameters like timeout, include_html, max_elements, or max_text_chars. The term 'bounded' hints at limits but does not clarify individual parameter semantics. Parameters are largely self-explanatory from names/defaults, but the description adds minimal value.

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, using a specific verb ('Return') and resource. It distinguishes itself from siblings like page_snapshot (whole page) and frame_list/frame_find (frame enumeration) by focusing on frames and boundedness.

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 clear context: use when you need a snapshot of a specific iframe/frame, not the entire page. However, it does not explicitly mention alternatives or exclusions, so agents must infer from the name and siblings.

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