vrm_download_installation_data

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

With no annotations provided, the description must fully disclose behavioral traits. It mentions 'Download' and 'optional parsing' but omits whether the action is safe (read-only), requires authentication, has rate limits, or what happens to existing data. The lack of any behavioral caveats is a significant gap.

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 concise sentence that front-loads the core action. It avoids unnecessary words. However, it could be slightly expanded to include the required parameter (siteId) without losing conciseness.

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?

Given the tool has 6 parameters, no output schema, and no annotations, the description is insufficient. It does not explain what the download returns (e.g., file content, URL), error scenarios, or how parameters like date range affect output. A more complete description would cover these aspects.

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 coverage is 100%, so the baseline is 3. The description adds no parameter-level information beyond what the schema already provides. It alludes to 'various formats' and 'optional parsing' but does not link these to specific parameters (format, decode). No added semantic value.

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 ('installation data') and specifies formats (CSV, Excel) and optional parsing, distinguishing it from sibling download tools like vrm_download_gps_data which download a different data type. However, it could more explicitly differentiate from non-download data retrieval tools like vrm_get_historic_data.

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 no guidance on when to use this tool versus alternatives (e.g., vrm_get_historic_data for non-file output). No prerequisites or context are mentioned, leaving the agent without contextual selection criteria.

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