Fetch the scene splat to disk

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

Annotations already provide readOnlyHint=true, and the description adds client-side behavior: it downloads the original file to disk and returns the path. It does not imply server-side mutation or hidden side effects, so it aligns with the annotation while adding context beyond it.

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 short sentences, with the core action first and the alternative guidance second. There is no filler, repetition, or unnecessary detail.

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 download tool with a readOnlyHint annotation, the description covers the core behavior, the returned path, and when to route to LOD alternatives instead. The only notable gap is explicit parameter explanation, which is already accounted for in the parameter semantics score.

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%, and the description never explicitly maps scan_id or out_path to their roles. While 'to a local file' and 'return the path' hint at out_path, the optionality/default behavior of out_path and the exact meaning of scan_id are left to inference, which is insufficient at this coverage level.

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 the action ('Download') and resource ('the scene's original splat.ply') and specifies the output ('to a local file and return the path'). It also differentiates itself from render-sized variants and names the LOD/artifact_fetch alternative, so distinguishing from siblings is straightforward.

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 explicitly tells the agent when not to use this tool: 'For a render-sized variant prefer the LOD levels (scene_lod → artifact_fetch of a level key).' This is direct routing guidance to an alternative, leaving no ambiguity about which tool to select.

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