gangtise_knowledge_resource_download

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

With no annotations, the description should fully disclose behavior. It only states the action (download) but does not mention whether it is read-only, what is returned (file content, URL, etc.), permissions needed, or any limitations. The date prefix in the description is unrelated and may be confusing.

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 core description is very short (one sentence), which is concise, but it includes an extraneous date note that does not belong to the tool's purpose, reducing structural clarity.

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 no output schema, the description should explain what the download returns. It does not address return format, error handling, or required steps (e.g., prerequisite call to gangtise_knowledge_batch). The description is too minimal to fully guide an AI agent.

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% and the schema's description already notes that resourceId comes from gangtise_knowledge_batch. The tool description adds no additional parameter meaning beyond the schema, so baseline 3 is appropriate.

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 explicitly states '下载知识库资源文件' (download knowledge base resource file), which specifies a clear verb and resource. It distinguishes from sibling download tools like gangtise_announcement_download or gangtise_drive_download by indicating the resource type as knowledge base.

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 other download tools in the sibling list. No context about prerequisites, conditions, or when to prefer this tool is given.

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