Unlock Notices

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

With no annotations the description carries the full burden, and it discloses useful behavior: exact title-filter keywords, returned fields only (art_code/title/date, no scale/ratio/shareholder data), empty-list behavior when nothing matches, and the data source (东财公告接口). Pagination/rate-limit behavior is not described, keeping it below a 5.

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?

Front-loaded with purpose and the filter criteria, with the output contract and sibling handoff following logically. Slightly padded by the skill reference and compliance boilerplate (只陈述事实，不做买卖推荐), but nothing is truly wasted.

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?

An output schema exists so return values need not be re-explained, and the description covers filtering, chaining to ann_content, and empty-result handling. The only real gap is parameter meaning, which is left entirely undocumented.

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 0% and neither parameter is explained: the description never clarifies that code is the target security identifier or what page_size controls. For a 2-param tool with no schema-level documentation, the description fails to compensate.

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?

States a specific verb and resource (search/filter unlock announcements by title keywords) and enumerates the exact match strings. It also scopes the output (art_code/title/date) and explicitly routes body-content needs to the sibling ann_content, so an agent can distinguish it from ann_list and ann_content without opening schemas.

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?

Explicitly ties the tool to a workflow (解禁冲击评估 / laogu-unlock skill) and states when-not to rely on it: 抛压定级需正文数据，本 tool 只做公告定位，用 ann_content 另取. The alternative and the condition that selects it are named.

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