editor_screenshot

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

Since no annotations are provided, the description provides vital behavioral context. It explicitly mentions the environmental restriction (not headless mode) and a dependency on external state (output directory must exist).

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 concise, stating the function in the first sentence followed immediately by the critical operational constraints in the second.

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 that the output format (PNG) and the necessary preconditions (existing directory, non-headless environment) are all detailed, the definition is contextually complete for an agent.

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?

The schema already provides a thorough description of the 'path' parameter (absolute/relative, .png). The description does not add further semantic meaning to the path itself, relying on the schema for structure.

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 tool clearly states its action: 'Captures the visible Flax Editor scene viewport to a PNG file.' This is specific and immediately distinguishes it from other editor functions like saving or manipulating actors.

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 two explicit conditions that dictate when this tool can or cannot be used: the output directory must exist, and it is unavailable in headless mode.

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