Fetch a synthetic view image

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

Annotations declare readOnlyHint=true, and the description adds valuable behavioral context beyond that: the result is a rendered PNG rather than a photograph, and the agent should explicitly say so when citing it. This is a useful disclosure about the nature and appropriate framing of the output.

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 a single, tightly written sentence. It front-loads the output type ('One synthetic view PNG') and includes the most important caveat ('not a photo') along with an actionable instruction for citation. There is no wasted text.

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 simple two-parameter read-only fetch, the description is mostly adequate: it names the output type and the render-versus-photo distinction. However, with no output schema and no parameter descriptions, an agent is left to infer how scan_id and view_id are used and where view_id comes from, so some guidance 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 0%, so the description carries the burden of explaining the parameters. It does not explain what scan_id or view_id mean, what format they take, or how to obtain a valid view_id. The parameter names are somewhat self-explanatory, but the description adds no semantic value for them.

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 title 'Fetch a synthetic view image' plus the description 'One synthetic view PNG' clearly identify the tool's resource and output. The phrase 'a RENDER of the splat, not a photo' also helps distinguish this from camera/keyframe images, though it does not explicitly name sibling tools.

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 implies the tool is for retrieving a single synthetic rendered view, and the 'not a photo' caveat helps set expectations. However, it does not explicitly state when to use this tool over alternatives like scene_keyframe_image or scene_synthetic_views, nor does it mention that view_id likely comes from scene_synthetic_views.

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