gangtise_announcement_download

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

No annotations provided, so description carries full burden. States it downloads files, but lacks details on error handling, permissions, or side effects. Minimal but accurate.

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 concise, but it is prefixed by a lengthy date processing instruction that is not specific to this tool, reducing efficiency. The main sentence is front-loaded but could be cleaner.

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?

No output schema, and description fails to explain what the tool returns (e.g., file content, URL, format). Lacks information on file size, encoding, or behavior on failed download. For a download tool, this is a significant gap.

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 baseline is 3. Description adds value by clarifying that announcementId originates from gangtise_announcement_list, which aids understanding. fileType is adequately described in schema.

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?

Description clearly states verb (download), resource (A-share announcement file), and key parameter (announcementId). Distinguishes from sibling tools by specifying 'A股' (A-share), unlike Hong Kong variants.

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?

Explicitly mentions that the announcementId comes from gangtise_announcement_list, providing a prerequisite. However, does not state when not to use it or explicit alternatives (e.g., Hong Kong counterpart).

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