Get 3D Screenshot

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

Annotations declare readOnlyHint=true, and the description adds that camera overrides are applied only to the capture, leaving the live view unchanged. No contradictory or missing behavioral traits.

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?

Single paragraph, front-loaded with main purpose. Every sentence adds value. Minor wordiness ('Requires a 3D map view to be open...') but still efficient.

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?

Covers prerequisites, parameter meanings, and behavioral nuance. No output schema, but 'inline image' implies return type. Could add that result is a base64-encoded image, but not essential given good annotations and schema.

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?

With 0% schema description coverage, the description fully compensates: explains dpi default, pitch range (0-90 with examples), heading as compass degrees, distance in metres, view_index for selecting among multiple views.

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 it captures an OPEN 3D Map View as an inline image, explicitly distinguishing from get_canvas_screenshot which cannot capture the OpenGL 3D view. The verb 'capture' and resource '3D Map View' are specific.

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 explicit context: requires an open 3D map view, gives menu path, and explains parameter usage. It implicitly excludes use when no 3D view is open and distinguishes from get_canvas_screenshot.

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