ie_screenshot

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

No annotations are provided, so the description must fully disclose behavior. It covers output as an image, PNG format, and optional save, but lacks details on error handling (e.g., missing element), prerequisites (visible window), and side effects. This leaves gaps for an agent to anticipate behavior.

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?

Single, well-structured sentence that front-loads the main action and linearly adds optional details. No wasted words; every phrase adds value.

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 no output schema and no annotations, the description should provide more context about return behavior, error states, and parameter interactions. It mentions two modes but omits details on when one might fail or what happens with missing elements. Parameter 'frame' is left unexplained.

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?

Description clarifies that by/value are used for element screenshots and save_path for optional saving, but fails to explain the 'frame' parameter (no schema description) and 'no_inline' (schema description exists). With 60% schema coverage, description adds moderate value but misses critical parameters.

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: capturing a PNG screenshot of the IE-mode window or a single element using by/value. It distinguishes itself from sibling tools (no other screenshot tool present) and provides specific details on output format and optional saving.

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 two usage modes (full window vs. element screenshot) and optional save_path, but does not explicitly state when to use which mode or provide exclusions. Sibling tools offer no alternative screenshot functionality, so the tool is effectively unique.

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