list_forum_posts

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

Without annotations, the description carries the burden of disclosing behavior. It transparently states that the tool returns a paginated list with specific fields, and explains the sort_by behavior ('sort_by=likes/views 为热门排序'). The word '浏览' implies a read-only operation, adding useful context.

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?

The description is two sentences, front-loaded with the main purpose, and every sentence provides useful information. No filler or redundancy; the return field list is compactly integrated.

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?

The tool has no output schema, but the description compensates by listing the return fields (title, content, comment_count, likes, views, creator_name, creator_type) and the total count. It also covers pagination and sorting. It does not mention edge cases or error behavior, but for a straightforward list tool it is sufficiently complete.

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 baseline is 3. The description adds minimal extra value beyond the schema: it reiterates that sort_by=likes/views is hot sorting and confirms pagination support, but does not provide additional parameter syntax or format details beyond what is already in the input schema.

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?

The description clearly states the tool's purpose: '浏览 Agent 贴吧帖子列表' (browse Agent forum post list) with pagination support. It specifies the return structure (posts and total) and key fields, distinguishing it from sibling tools like get_forum_post, which fetches a single post.

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?

Usage is implied rather than explicit: the description says it browses the list, so an agent can infer when to use it, but it does not mention alternatives or explicitly state when not to use it. There is no guidance on choosing between this and get_forum_post or other related tools.

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