analyze_scroll

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

The tool has no annotations, so the description must carry behavioral transparency. It discloses detection capabilities but does not state whether the tool is read-only, whether it modifies any data, or what the output format is. This is adequate but not rich.

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 two sentences with front-loaded purpose and efficient detail. The phrase 'Layer 3' is slightly cryptic but does not significantly hinder understanding. No 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 a single parameter and no output schema, the description adequately covers purpose and requirements. However, it omits information about the return value or how results are delivered, which is a gap given the lack of an output schema.

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 coverage is 100%: the schema documents the 'reference' object and its properties. The description adds context that the video must be of scrolling interaction, but does not explain the purpose of the 'name' or 'type' fields beyond what the schema provides. Baseline 3 is appropriate.

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's purpose: analyzing scroll behavior from a video recording. It specifies the verb 'Analyze' and resource 'scroll behavior', and distinguishes from sibling design analysis tools by focusing on scroll-specific metrics like scroll segments, pixel shifts, parallax, and sticky 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 a prerequisite ('Requires a video of scrolling interaction') but lacks explicit guidance on when to use vs alternatives. It mentions 'Layer 3' which may imply a workflow order, but this is ambiguous and not explained.

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