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

No annotations are provided, so the description carries the burden, and it only implicitly signals the operation is a harmless read of a built-in static list ('内置'). It says nothing about return format, ordering, pagination, or whether any auth is required, which is a modest gap for a zero-parameter list tool.

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?

A single short sentence that front-loads the action and resource, with the cross-tool relationship tucked into a parenthetical. No wasted words.

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?

With no output schema and no annotations, the description should carry the full picture, but it only hints that names are returned and never describes the actual shape of each preset entry. Adequate for such a simple tool, but incomplete.

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?

The tool takes zero parameters, so per the baseline there is nothing for the description to disambiguate. The parenthetical about pack names being usable in scan_accounts adds a little semantic value about what the returned values mean.

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?

Names a specific verb and resource ('列出内置精选账号包'), and the parenthetical clarifies it is the source of pack names consumed by the sibling scan_accounts, so it is distinguishable from get_post, reset_seen, and search_x_news. An agent can tell what this returns without opening the schema.

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 note that scan_accounts can reference the pack names directly conveys when this tool is useful (as a discovery step feeding scan_accounts). It gives clear context but stops short of an explicit 'call this before scan_accounts' instruction or any exclusions.

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