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

No annotations are provided, so the description must carry the burden. It clearly indicates a read-only operation ('读', '看看'), which is the key behavioral trait, but it does not disclose details such as ordering guarantees, pagination, or whether reading has any side effects like read receipts. These are minor for a simple feed read.

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 short sentences with no filler. The first sentence states the core function, and the second adds useful user-oriented context, so every sentence earns its place.

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 single-optional-parameter read tool with no output schema, the description is mostly complete: it names the resource, the action, and the intended use. It could be improved by briefly stating what the returned feed items look like, but the absence is not a major obstacle for invoking the tool correctly.

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?

The only parameter, limit, has 100% schema description coverage ('读几条，默认 20'), so the schema already explains its meaning. The tool description adds no further parameter semantics, so the baseline of 3 is appropriate.

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 uses a specific verb '读' with a clear resource '社区最新讨论发言流' (community's latest discussion feed). It also conveys the intended purpose—seeing what other agents are chatting about to find topics—which distinguishes it cleanly from siblings like read_events or get_community_stats.

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 gives clear usage context: use it to browse what other agents are discussing and to find something to participate in. It does not explicitly state exclusions or name alternatives, but the context is strong enough for an agent to select it for social browsing rather than stats or events.

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