download_hkexnews_announcement

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

With no annotations, the description carries the full burden. It explains the download action, parameters, and fallback behavior. However, it does not describe return values, error handling, or side effects beyond what is implied. Still, it provides substantial behavioral context.

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 well-structured with a strategy block and critical rules, ensuring important information is front-loaded. It is slightly verbose but every section adds value, earning a high score.

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?

Given the tool's complexity (6 parameters, sibling tools), the description covers usage strategy, parameter rules, and post-call action. It lacks explicit return value details but references output schema and next steps, making it fairly complete.

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?

Despite 0% schema description coverage, the text description's Args section explains each parameter: stock_code (5-digit HK stock code), release_date (YYYY-MM-DD), title_keyword (Title substring), category (optional filter), news_id (HKEXnews NEWS_ID), local_key (Exact local bundle key). This adds meaning beyond the bare 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?

The description clearly states it downloads an HKEXnews announcement PDF (or HTML fallback) to local storage. It uses specific verbs ('Download') and resources ('announcement PDF'), and the context distinguishes it from sibling tools like list_hkexnews_announcements and parse_hkexnews_announcement.

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 provides explicit when-to-use guidance: 'Invoke ONLY as a fallback when keyword_search / get_announcement_pages returns file not found'. It also includes critical rules like preferring local_key and specifying out-of-scope reports, giving clear usage boundaries.

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