Screenshot

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

With no annotations, the description carries the full behavioral burden and delivers real value: it discloses that capture bypasses window occlusion and that each image costs ~1K tokens, a meaningful rate/cost signal. It omits any permission or error behavior and does not state what is actually returned, so it stops short of fully covering the operation.

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 tight sentences with zero waste: the capture semantics come first, then usage, then the cost caveat. Every clause contributes information an agent needs.

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?

For a one-optional-parameter read tool with no output schema, the description supplies the key operational facts (what is captured, why to call it, token cost). It could note that the result is image content and any failure modes, but nothing essential to invoking it correctly is missing.

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% ('Opiumware port of the Roblox instance'), so the sole optional parameter is fully documented in structured form. The description adds no port-selection guidance, which is the baseline expectation when the schema does the heavy lifting.

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?

States a specific verb+resource ('Capture the Roblox window') plus a distinguishing qualifier ('as the player sees it, works even if other windows cover it'). This cleanly separates it from siblings like logs, network, scripts, execute, and status, which retrieve non-visual data.

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?

Gives a concrete use case ('Use to verify visual scripts (ESP, UI, menus)') and a frugality constraint ('use sparingly') driven by token cost. It stops short of naming an alternative or an explicit when-not-to-use condition, so it is clear context rather than full routing guidance.

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