babylonjs_screenshot

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

With no annotations present, the description carries the burden of behavioral disclosure. It clearly states that screenshots are saved to tmp/, that file paths are returned, and that a rendering browser is required. It does not cover failure modes, file naming, cleanup, or error cases, so it stops short of a 5.

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?

Three substantive sentences with no filler. The core action is front-loaded, followed by capabilities, output behavior, and a precondition. Every sentence 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?

For a screenshot tool with no required parameters and a nested optional customCamera object, the description covers purpose, output location, returned values, and a critical prerequisite. It is slightly light on the exact shape of returned paths and how multiple views map to outputs, but an agent still has enough to select and invoke it correctly.

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 only 20%, with only customCamera described. The description partially compensates by explaining that multiple views, preset angles, depth maps, and custom camera positions are supported, but it does not add meaningful semantics for width, height, format, or the individual view enum values beyond what the schema already exposes.

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 states a clear action and resource: 'Capture one or more screenshots of the BabylonJS scene.' It also names concrete capabilities (preset angles, depth maps, custom camera positions) that distinguish it from scene inspection or connection tools, though it does not explicitly contrast it with a sibling.

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?

It provides an explicit precondition and negative condition: 'Only available when a browser with rendering is connected.' This helps the agent avoid calling it at the wrong time. It implies use whenever a visual snapshot is needed, but it does not name alternative tools or when to prefer them.

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