spa_screenshot

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

With no annotations provided, the description carries full behavioral burden. It discloses DOM stabilization wait but omits important traits such as output format, storage location, authentication needs, or limitations (e.g., page size). This leaves significant gaps.

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?

Two concise sentences with no wasted words. Information is front-loaded and easy to parse.

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?

Despite 7 parameters, the description is minimal. It does not clarify parameter relationships (e.g., fullPage vs selector exclusivity), return format (no output schema), or session management. Incomplete for a tool with many options.

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 has 100% coverage, so all parameters are described. The description adds marginal value by explaining why DOM waits (for stability), but it does not elaborate on parameter interactions or defaults beyond what schema provides.

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 it takes a screenshot, specifies SPA framework support, and mentions waiting for DOM stability. This distinguishes it from generic screenshot tools and aligns with sibling tools focused on SPA interactions.

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 implies use for SPA screenshotting but does not provide explicit when-to-use or when-not-to-use guidance. Among siblings, it is the only screenshot tool, so context is implicit but not articulated.

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