gangtise_foreign_report_download

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It states supported formats but does not mention side effects, authentication requirements, rate limits, or what happens if the reportId is invalid. The tool likely performs a read operation, but this is not explicitly stated.

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 functional description is a single sentence listing formats, but it is prefixed by a date/time bracket note that is not directly related to tool behavior. This adds noise and reduces conciseness. The structure could be cleaner without the prefix.

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 lacks information about the return format (e.g., binary data, URL, or file content) and authentication needs. With no output schema and many sibling tools, the description is incomplete for an AI agent to fully understand how to handle the tool's output.

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%, with both parameters already described in the schema. The description adds no new meaning beyond that, as it restates the fileType options already covered. Baseline score of 3 is appropriate since the schema does the heavy lifting.

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 downloads foreign research reports and lists supported formats (PDF, Markdown, Chinese PDF, Chinese Markdown). It distinguishes from the list tool (gangtise_foreign_report_list) but does not explicitly differentiate from other download tools like gangtise_research_download. The verb 'download' and resource 'foreign research reports' are specific.

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 implies that the tool is used after obtaining a reportId from gangtise_foreign_report_list, but it does not provide explicit guidance on when to use vs not use this tool, nor does it mention alternatives or prerequisites beyond the reportId. Usage context is clear but not comprehensive.

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