gangtise_record_download

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention that the operation is read-only, safe, or any potential side effects. The description merely restates the schema, missing transparency on authentication or limits.

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 includes an unnecessary date context prefix that is not relevant to the tool's purpose. The core sentence is concise, but the extraneous note reduces efficiency.

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?

The description covers the tool's function and main parameters, but lacks information about the output format (e.g., file download, raw data). Without an output schema, the description should hint at what the agent receives.

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%, but the description adds value by explaining the options for contentType ('可选原始音频、ASR文字或AI摘要') and implying that recordId comes from the list tool. This goes beyond the schema's concise descriptions.

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 ('下载') and the resource ('语音录音转写内容'), with specific options (原始音频、ASR文字、AI摘要). It distinguishes from sibling download tools (e.g., gangtise_announcement_download) by targeting record content.

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?

No explicit guidance on when to use this tool vs alternatives. The schema indicates recordId comes from gangtise_record_list, which implies a prerequisite, but the description does not state it. Context is adequate but lacks exclusions.

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