snapshot

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

Annotations already cover the safety profile (readOnly, non-destructive, openWorld), so the bar is lower. The description adds real value beyond them by disclosing the return artifacts (MCP image plus saved PNG and hash) and an important semantic caveat that the capture does not prove upload or visibility to others.

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, front-loaded with what is captured and returned, followed by the caveat. No filler and every clause earns its place.

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?

With no output schema, the description usefully covers return values and adds a meaningful limitation. However, for a 6-parameter tool with 0% schema coverage, the complete absence of parameter semantics leaves an agent guessing about layer, dimensions, and UI/HUD toggles.

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 0% across 6 parameters (label, layer, width, height, show_ui, show_hud), and the description says nothing about any of them. With low coverage the description must compensate, and it provides zero parameter meaning.

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 (capture) and resource (Firestorm's rendered image) and even names the outputs (MCP image, saved PNG, hash). It does not differentiate itself from the related sibling capture_orbit, which likely also produces rendered captures, so it falls short of a 5.

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?

There is no explicit when-to-use guidance and no routing to alternatives such as capture_orbit or image_compare. The closing caveat about render evidence not proving upload/visibility is an interpretive warning, not usage direction, so guidance remains largely absent.

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