simscale_download

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

Annotations already declare non-read-only and non-idempotent behavior. The description adds valuable context: the file save location (SIMSCALE_FILE_ROOT/simscale-downloads) and the confirmation requirement. This goes beyond the structured annotations without contradicting them.

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 two sentences, front-loads the primary action, and gives the save destination and a required flag. No unnecessary words or repetition.

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 download tool with two parameters (one nested object well-described in schema) and no output schema, the description covers the essential information: purpose, save location, and required flag. It lacks details like error handling or overwrite behavior, but these are not critical given the tool's simplicity and annotation 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 coverage is 50%, and the description compensates by explaining confirm_download (must be true). The target parameter is already described in the schema as a stable, visible UI target with preferred locators. The tool description's reference to a 'unique SimScale download control' reinforces the target's purpose.

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 tool's function: clicking a unique SimScale download control and saving the result under a specific path. It distinguishes itself from sibling tools like simscale_click by specifying the download-and-save behavior.

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 conveys a requirement (confirm_download=true) and implies use for downloading a SimScale control, but it does not explicitly mention when to use this tool over alternatives like simscale_click or how to decide between them. No exclusions or alternative tool references are provided.

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