gangtise_research_download

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

No annotations are provided, so the description carries the full burden. It states the output format but does not disclose any behavioral traits such as being read-only, permissions needed, or rate limits. For a download tool, additional transparency about side effects or limitations would be expected.

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 is a single sentence but includes a date hint that is not directly relevant to the tool's function. The hint adds overhead and could be placed elsewhere. The purpose is stated clearly, but the structure 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?

The description explains the output (Markdown text or PDF file path) but lacks specifics about the Markdown structure or PDF path format. With no output schema, more detail would improve completeness, but the description is adequate given the straightforward nature of the tool.

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 description coverage is 100%, so the baseline is 3. The description adds context by linking reportId to gangtise_research_list and clarifying fileType values (1=PDF, 2=Markdown), but this information is already present in the schema's parameter 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 verb 'download', the resource 'brokerage research reports', and the output 'Markdown text or PDF file path'. It distinguishes from sibling tools like gangtise_research_list (lists reports) and gangtise_research_outline (likely provides outlines).

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 mentions that the reportId comes from gangtise_research_list, which implies a prerequisite but does not provide explicit when-to-use or when-not-to-use guidance. No alternatives are mentioned.

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