screenshot

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

No annotations provided. Description only specifies the display (DISPLAY=:10) and adds an implementation reference, but fails to disclose permissions, failure modes, or effects like whether it captures full screen or window.

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 sentences; the first is essential and clear. The second sentence adds implementation context but is not critical. Still concise overall.

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?

No output schema, so description should provide more detail on the returned data (e.g., size, details) or behavior (e.g., asynchronous, permissions). States only output format. Incomplete for a tool with zero annotations.

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?

No parameters, so baseline 4. The description already states the output format, which is useful beyond the empty 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?

Clearly states verb 'capture', resource 'active display', and output format 'base64-encoded PNG'. Distinguishes from sibling tools that perform other actions like clicking or moving.

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?

No guidance on when to use this tool vs alternatives. Does not mention when not to use or provide context for selection.

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