list_hkexnews_announcements

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

No annotations provided, so description carries full burden. Discloses exclusion of periodic report PDFs (t1=40000), inclusion of performance announcements, and limit max 50. Does not mention auth, rate limits, or error handling, but for a list operation the disclosure is fairly comprehensive.

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?

Highly concise with structured sections (intro, strategy, critical rules, args). Every sentence adds value. No redundancy.

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 6 parameters, no annotations, and an output schema exists, the description provides sufficient context: explains when to use, what is excluded/included, and parameter details. Complete for an AI agent to use correctly.

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 0%, so description must compensate. Provides detailed parameter descriptions with examples (e.g., '00700', 'Inside Information'), format YYYY-MM-DD, defaults, and max limit. Adds significant meaning beyond 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?

Clearly states 'List available HKEXnews announcements for a company' with specific verb and resource, and crucially excludes full periodic report PDFs, distinguishing it from general listing tools.

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?

Contains explicit strategy section: use for discovering metadata before download; skip if user provides specific date/title and instead use keyword_search or download_hkexnews_announcement. Provides clear alternatives.

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