get_screenshot

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only restates the basic function ('Get the screenshot image') and does not mention return format, error behavior, or any side effects. For a tool that retrieves a resource, more detail is needed (e.g., whether it returns binary data or a URL, what happens if the ID is invalid).

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 a single, clear sentence that is front-loaded with the action and resource. It contains no redundant words and is appropriately concise for the tool's simplicity.

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 tool is simple (one parameter, no output schema, no annotations), so the description is mostly adequate. However, since there is no output schema, the description should clarify what 'screenshot image' means as a return value (e.g., binary, path, URL). This missing detail prevents a higher score.

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 description coverage is 100% – the schema already explains the 'id' parameter as 'The annotation ID'. The description adds no additional meaning beyond this, so the baseline of 3 applies.

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 action ('Get the screenshot image'), the target resource ('for a specific annotation'), and the scope ('by ID'). This distinguishes it from sibling tools like get_all_pending (which lists pending items) and resolve (which likely acts on annotations).

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 usage when you have an annotation ID and need its screenshot, but it does not explicitly state when to use this tool versus alternatives or provide any exclusions. No mention of when not to use or prerequisites beyond the ID is given.

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