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

No annotations are provided, so the description carries the full disclosure burden. It usefully states what is returned (id/平台/昵称/状态), but omits auth requirements, whether results are paginated or sorted, and what an empty list means (no bound accounts vs. error).

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 sentences, front-loaded with the verb and resource, followed by the return fields and the code table. Every element earns its place; no filler.

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?

For a one-parameter list tool with no output schema, the description covers purpose, returned fields, and the platform code vocabulary needed to use the filter. Remaining gaps (pagination, empty-result semantics) are minor.

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 coverage is 100% and the single parameter is self-documented as an optional filter defaulting to all platforms. The description adds real value beyond the schema by supplying the valid platform codes (douyin, xiaohongshu, weixinshipinhao, kuaishou, guanghe, bilibili, tiktok_desktop), which the schema does not enumerate as an enum.

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 (列出/list) and resource (用户已绑定的自媒体矩阵账号) plus the downstream purpose (发布视频用), and enumerates the returned fields. It does not explicitly compare itself to any sibling, but the siblings are largely unrelated operations, so the risk of mis-selection is low.

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 parenthetical '(发布视频用)' implies the context in which this list is needed (before publishing a video), but there is no explicit when-to-use or when-not-to-use statement, and no alternative tool is named. Usage is inferable rather than spelled out.

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