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

With no annotations, the description carries the behavioral burden. It usefully discloses sort order (发布时间倒序) and the exclusion of article bodies (不返回正文), which routes the agent to get_article for content. However, it says nothing about auth requirements, rate limits, or maximum result behavior beyond the schema's page_size cap.

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?

Three terse, front-loaded sentences: scope+pagination first, filters second, the important exclusion (不返回正文) last. Nothing is wasted and no sentence merely restates the tool name.

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?

No output schema and no annotations, so the description must carry the load, and it covers scope, ordering, filtering dimensions, and what is omitted from results. It is nearly complete for a paginated list tool, missing only guidance on choosing it over the sibling search/list tools.

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%, so the schema already documents all six parameters (q, tag, page, year, category, page_size). The description restates the filter dimensions at a high level but adds no syntax or format detail beyond the schema, matching the baseline-3 case.

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 (分页浏览航通社全站文章), plus sort order and scope (全站), so an agent can distinguish it from get_article (single item) and search_articles. It stops short of naming those siblings explicitly, so differentiation is inferred rather than stated.

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 description implies the browsing use case via '分页浏览全站文章' and lists supported filters, but never says when to prefer this over search_articles or get_article. Usage is implied by scope, not spelled out as an explicit rule.

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