scout_scan

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it describes what the tool scans in each mode, it lacks information on potential side effects, timeouts, execution context (e.g., whether JavaScript runs), or required permissions. This is adequate but not comprehensive.

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, using bullet points to clearly delineate the two modes and their sub-components. Every sentence is informative and avoids redundancy, making it easy to scan.

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 (not shown but indicated), the description does not need to detail return values. It sufficiently covers the tool's two scanning modes and the role of each parameter. A minor gap is the lack of mention of pagination or error handling, but overall it is complete for the tool's 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?

The schema description coverage is 100%, and the description adds value by explaining how each parameter relates to the two modes. For example, it clarifies that 'url' is optional for mode 'dom' and 'keyword' is used for DOM search. This goes beyond the schema's basic parameter descriptions.

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 as a 'comprehensive page data source scanner' with two explicit modes ('all' and 'dom'), each with a detailed breakdown of what it scans. This provides a specific verb-resource combination that distinguishes it from sibling tools like scout_apis or scout_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 explains the two modes and their purposes, giving clear context for when to use each. However, it does not explicitly state when not to use this tool or provide direct comparisons to alternatives, which would be helpful for a complete usage guideline.

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