fidelity_screenshot

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the tool may navigate to a URL before capturing, but omits authentication/session prerequisites, whether it affects the current page state, and what form the screenshot result takes.

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 short sentences with no filler, and the core action is front-loaded. The optional URL behavior and debugging purpose each add useful information without repetition.

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 simple one-parameter tool, the core action and optional URL behavior are covered. However, with no annotations and no output schema, the description should ideally clarify login/session requirements and the screenshot return format; those gaps leave it only minimally complete.

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 single parameter is only a bare 'url' string in the schema with 0% description coverage. The description compensates by explaining that the URL is optional and, when supplied, is a Fidelity URL opened before the screenshot, which adds useful meaning beyond the schema.

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 verb and resource: screenshot the browser page. It also clarifies the optional URL behavior and frames the purpose as selector debugging. It does not explicitly differentiate from siblings such as fidelity_page_content, but the screenshot/debugging intent is clear.

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 phrase 'For debugging selectors' gives a clear use case, and 'optionally after opening a Fidelity URL' explains the main calling context. It does not name alternatives or when-not-to-use cases, but the intended usage is not left entirely implicit.

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