gangtise_foreign_report_list

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

No annotations provided, so description bears full burden. It mentions filters but does not disclose pagination behavior, rate limits, or result size constraints. The existence of 'size' and 'fetchAll' parameters hints at pagination, but description does not explain performance implications or defaults.

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?

Single sentence with a date hint is efficient and front-loaded. However, the date hint is placed at the beginning and could be seen as meta-instruction rather than tool behavior; it would be better placed in a separate note. No wasted words.

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?

With 18 parameters, no output schema, and no annotations, the description is insufficient. It does not explain return value structure, how to interpret the list, or how pagination works. For a complex query tool, more detail on expected output and parameter semantics is needed.

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 low (39%). Description lists filter categories (e.g., securities, region, industry, broker, rating) which adds some meaning beyond bare parameter names, but many parameters (e.g., llmTagList, ratingChangeList, minReportPages) remain unexplained. The regionList description notes values come from gangtise_lookup, but other lists lack similar guidance.

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 the verb '查询' (query) and resource '外资机构研报列表' (foreign institution research report list), and lists multiple filter dimensions (证券、地区、行业等). It effectively distinguishes from sibling tools like gangtise_research_list (domestic) and gangtise_foreign_report_download (download).

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?

Description implies usage for listing foreign research reports but provides no explicit guidance on when to use this tool vs. alternatives (e.g., gangtise_foreign_opinion_list, gangtise_research_list). No when-not-to-use or contextual exclusions.

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