anon_get_materials_resource_id_versions_version_download

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: the response is served as an attachment via Content-Disposition, and access is gated on project membership plus visibility scope. It does not cover error or missing-file behavior, which keeps this from a 5.

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?

Front-loads the action ('下载指定版本原文件') and then layers access, response, and endpoint details in short clauses. The raw HTTP path is somewhat redundant with the tool name but is compact and harmless.

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?

With no output schema, the description correctly explains what the caller receives (a downloadable attachment) and what authorization is required, plus the implicit project scoping. Only failure modes and any pagination/size limits are unaddressed, which is a minor gap for a download endpoint.

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?

The schema has 0% description coverage and a nested path object, so the description must compensate. It clarifies that resourceId identifies the material and version selects the version, and that no projectId is required, but it adds no format, bounds, or validation detail beyond what the schema implies.

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?

States a specific verb and resource: download the original file for a specified material version ('下载指定版本原文件'), which is enough to separate it from the preview siblings by the word '原文件'. It does not name those siblings, so an agent must infer the download-vs-preview distinction, but the purpose itself is unambiguous.

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?

Gives an access prerequisite ('项目成员且通过可见范围校验') and notes the project is derived from the API key, so no projectId is needed. However, it never states when to prefer this tool over anon_get_materials_resource_id_versions_version_preview or anon_get_materials_resource_id_versions, leaving the choice implied rather than guided.

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