gangtise_announcement_hk_list

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

No annotations are provided, so the description carries full burden. It only states basic query and filter capabilities, failing to disclose pagination behavior (though schema has size/fetchAll), result format, or any side effects. The date context note is about query interpretation, not tool behavior.

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 with a necessary date context note, no redundancy, and front-loaded key information. Every element serves a purpose.

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 10 parameters and no output schema, the description is insufficient. It omits details on pagination, keyword search behavior, search type differences, and expected output. A more complete description would explain how the tool works, e.g., 'returns a paginated list of announcements matching filters'.

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 60%; the description adds context by listing three filter types (security, category, time) matching parameters. However, it does not explain keyword, searchType, rankType, from, size, or fetchAll beyond what's in schema. The date note in startTime/endTime schema helps but is not from the description itself.

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 queries Hong Kong stock announcement lists with filtering by security, category, and time range, distinguishing it from siblings like gangtise_announcement_list (likely A-shares) and gangtise_announcement_hk_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?

The description implies usage for listing HK announcements with filters but does not explicitly state when to use alternatives or when not to use this tool. No exclusion criteria or alternative references are provided.

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