Fetch the scene point cloud to disk

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

The readOnlyHint annotation already signals no server-side mutation. The description adds that the tool writes a file locally and returns a path, which is useful. However, it does not disclose overwrite behavior, directory requirements, or what happens when out_path is omitted.

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?

A single, well-structured sentence that says exactly what the tool does and returns. Every word earns its place, and the key action is front-loaded.

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 read-only download tool, the description gives the essential action and return value. But because there is no output schema and no parameter documentation, the missing details about out_path behavior and sibling differentiation leave noticeable gaps for an agent deciding how to invoke it.

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 full responsibility for parameter meaning. It never mentions scan_id or out_path explicitly; 'scene's cloud.ply' and 'local file' hint at them, but the optionality and expected format of out_path are left unclear.

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 verb ('Download'), a specific resource ('scene's cloud.ply'), and the result ('to a local file and return the path'). It distinguishes this tool from splat or generic artifact fetchers by naming the point cloud file, but it does not explicitly compare against sibling tools like artifact_fetch or artifact_fetch_splat.

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?

No guidance is given about when to prefer this tool over artifact_fetch or artifact_fetch_splat. The description implies the use case by describing the operation, but it provides no context, conditions, or alternatives.

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