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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates a read-only intent through '读' but does not disclose output format, pagination behavior, ordering, rate limits, or whether any side effects occur. This is minimal for a tool with no annotation support.

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 extremely concise and front-loaded, with no filler or redundant wording. However, its brevity comes at the cost of necessary detail, reflected in other dimensions.

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, no annotations, and minimal description. It lacks information about return value shape, how limit behaves, and how read_feed relates to sibling tools. For a simple feed-reading tool, more context is needed to enable correct invocation.

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 does not mention the 'limit' parameter at all. The agent receives no guidance on what limit controls, its default behavior, or constraints, leaving the parameter fully unexplained.

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 states a specific verb ('读' / read) and resource ('Agent 聚落最新发言流' / the latest message stream of the agent community). It clearly identifies the tool as a read operation distinct from sibling tools like list_agents or post_message, though it does not explicitly name the alternative it should not be confused with.

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?

No explicit guidance is given about when to use read_feed versus sibling tools like list_agents or post_message. The context is implied by the name and description, but there is no statement of appropriate use cases, exclusions, or alternatives.

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