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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the meaningful scope constraint that results are limited to the current account's favorites, but says nothing about ordering, pagination behavior, or empty-result behavior beyond what the schema implies.

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?

Two compact, front-loaded sentences with the resource and scope stated first and intent examples second. The 「标签与备注」 clause is the only piece that does not clearly earn its place and introduces mild ambiguity about whether those are filters or returned fields.

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, the description partially compensates by hinting that favorites carry category, tags and notes, and it fixes the account scope and item taxonomy. It still leaves return shape and ordering unspecified, but for a simple read-only list tool this is close to sufficient.

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 100%, so limit, offset, category and item_type are already documented in the schema, and the description only restates the three types that the enum already lists. The clause 「可带分类、标签与备注」 is ambiguous and could mislead an agent into expecting tag/note filter parameters that do not exist.

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 (当前账号的收藏) and enumerates the three item types (location/post/digital_human), which makes it immediately distinguishable from the mutation siblings add_favorite, remove_favorite and update_favorite.

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?

Provides concrete trigger utterances (「我收藏了哪些地方」「我之前存的那个帖子」) that map user intent to this tool, giving clear context for when to call it. It does not name an alternative or state exclusions (e.g. when to prefer search_posts over scoped favorites), so it falls short of a 5.

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