Get announcements

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

Annotations already indicate readOnly, idempotent, non-destructive. Description adds valuable details: no body/html/prose returned, en/cn never mixed, returns empty list if feed not imported, results newest-first and paged. These go beyond annotations.

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?

Description is a single sentence with good information density. It could be split for readability, but it remains concise and front-loaded with the core 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?

No output schema, but description covers returned fields, region, date filtering, pagination, and behavior for missing data. Missing error handling or rate limits, but adequate for a read-only 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 has 0% description coverage, so description compensates by explaining since/until are ISO date bounds, pagination with page/page_size, and the server enum. It doesn't detail nested page object fields, but the explicit mention of paging provides adequate 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 explicitly states it lists official Arknights announcement metadata by region (en/cn), and distinguishes that it only returns metadata (announce_id, title, date, url, category) not body. This clearly differentiates from sibling tools which focus on enemies, operators, stages, etc.

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?

It indicates the tool is for listing announcement metadata from official news feeds, and that regions are never mixed. It doesn't explicitly state when not to use it, but the context of sibling tools makes the intended use clear.

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