Fetch batch snapshots

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

Annotations already declare readOnlyHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds one genuine trait beyond the annotations ('without overwriting'), but omits that files are written to the local disk and that non-idempotency means repeated calls create additional files, which is a notable gap for a download tool.

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 front-loaded sentence with no filler; the key constraint ('without overwriting') is stated early. It is efficient, though arguably too terse for a tool whose parameters and prerequisites are undocumented.

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?

An output schema exists, so return values need not be explained. But with 0% parameter coverage, no usage guidance, and an unstated prerequisite that run_id must reference a completed batch, the description is insufficient for an agent to invoke this correctly without external context.

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% for two required parameters, so the burden is entirely on the description, which never explains what run_id identifies (a batch run id?) or that dest_dir is the target directory. 'New local files' is only a weak hint at dest_dir, leaving run_id completely undefined.

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 verb+resource ('Download completed snapshots') is specific enough to convey the operation, and 'completed' hints the source is a finished batch run. However, 'snapshots' is never defined and the description does not distinguish this from sibling tools like revit_model_snapshot or revit_batch_status, so an agent must guess what artifact is being fetched.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative among the many batch/snapshot siblings. The only implicit condition is that snapshots must be 'completed', which is not tied to any prerequisite (e.g. a run_id from a finished job).

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