analyze_screen

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

No annotations are provided, so the description carries full responsibility. It mentions using Claude vision, but does not disclose that the tool may capture a new screenshot (as indicated by fresh_screenshot parameter) nor any side effects, permission needs, or limitations (e.g., only works with OSRS client visible).

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 sentence that efficiently conveys the purpose and capabilities. It is front-loaded with the verb and resource. Minor improvement possible by breaking into multiple sentences for readability, but overall concise.

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 or annotations, the description lacks critical context: it does not describe the output format (e.g., text analysis, JSON), the scenario when no screenshot is available, or whether the tool only works on OSRS client. It relies on parameter descriptions for the fresh_screenshot behavior but omits this from the main description.

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 coverage is 100% with descriptions for all three parameters. The description adds value by summarizing the focus options, but does not deepen understanding beyond what the schema already provides (e.g., no additional detail on what each focus entails).

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 analyzes a screenshot of the OSRS client using Claude vision and lists specific focus areas (inventory, stats, chat, etc.) and full analysis. It distinguishes itself from sibling tools like analyze_inventory by covering multiple foci, but does not explicitly contrast them.

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 provides no guidance on when to use this tool versus alternatives such as analyze_inventory, detect_combat_state, or capture_screen. It implies broad usage but fails to specify when a more specialized tool would be preferred or when not to use this tool.

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