take_screenshot

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

Annotations declare readOnlyHint=true, which is consistent with the screenshot operation. The description adds behavioral context by mentioning token cost differences for element vs full viewport, though it does not detail other traits like file format or size limits.

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 front-load the primary action and immediately provide a key usage tip. Every word adds value with no extraneous content.

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?

The description explains purpose and one parameter but omits details on 'frameId' and 'fullPage' behavior. With no output schema, it fails to describe the return format (e.g., base64 data). Cost optimization is noted, but overall scope is incomplete.

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?

With 0% schema description coverage, the description must explain all parameters. It only clarifies the 'target' parameter as a CSS selector for an element. 'frameId' and 'fullPage' are not explained, leaving gaps in understanding.

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 captures the viewport, full page, or a single element as a PNG image. It distinguishes between modes and highlights the token cost advantage of targeting an element, which differentiates it from siblings like snapshot.

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 advises using the target parameter to crop to an element for cost efficiency, contrasting it with a full viewport image. It does not explicitly cover when to use viewport vs full-page or alternatives among siblings, but provides useful context for decision-making.

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