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

With no annotations, the description carries the full burden; it does disclose that results are read-only raw comments with unified fields, which is real added value. It says nothing about pagination behavior despite a limit parameter, ordering of results, or what happens when a post has no comments.

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 short sentences with zero filler: the fetch purpose and output fields come first, the follow-up routing second. Nothing to cut.

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?

It covers output fields and next-step workflow, but for a 3-parameter tool with 0% schema coverage, no annotations, and no output schema, gaps remain around platform value space, limit/pagination semantics, and error behavior for a missing post.

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 the description only implies post_id via "某条内容"; platform and limit are never mentioned. No hint about valid platform values (a list_platforms sibling exists) or what limit controls, so the agent must guess at two of three parameters.

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+resource: fetching the comment list for a given piece of content, and adds that fields are normalized (commenter, content, likes, time). That implicitly separates it from the sibling get_comment_insights, which produces conclusions rather than raw comments, though it never explicitly says it is the raw-fetch counterpart.

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?

"拿到评论后用 get_comment_insights 出结论" gives an explicit downstream alternative and the condition that selects it, which is genuinely useful routing. It stops short of stating when not to use this tool or any prerequisites (e.g. needing a valid post_id from search_posts).

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