scout_page_tool

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

With no annotations provided, the description carries full burden. It implies a non-destructive reconnaissance operation but does not explicitly state it is read-only or safe. It explains the return type and detail levels but lacks disclosure of any side effects or permissions needed.

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 concise and well-structured, with a clear one-line summary followed by bullet points for arguments. It prioritizes the main purpose and provides necessary details 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?

For a tool with 3 parameters and no output schema, the description adequately covers the input parameters and general output (structural overview). It references a sibling tool for specific searches, making it contextually complete for an AI agent to understand when and how to use it.

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?

The schema coverage is 0%, so the description adds significant value by explaining the purpose of each parameter: session_id (from launch_session), focus_frame (optional iframe CSS selector), and detail_level with two enumerated options ('summary' vs 'full') and their implications on response size.

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 states a specific action ('Perform deep reconnaissance on the current page state') and clearly defines the output (structural overview with metadata, iframe hierarchy, shadow DOM boundaries, element counts). It also distinguishes from sibling 'find_elements' by directing the agent to use that tool for searching specific elements.

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 explicit guidance on when to use this tool (for structural overview) and references the alternative 'find_elements' for specific searches. However, it does not discuss when not to use it or mention any prerequisites beyond having a valid session_id.

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