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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates a read-only viewing action and identifies the data returned, which is useful, but it does not mention output format, staleness, access restrictions, or any side effects—though for a simple statistics getter this is a modest gap.

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 a single front-loaded sentence that conveys the resource, the action, and the specific metrics in only a few words. Every element earns its place with no redundancy.

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?

Given the tool's simplicity—zero parameters, no nested objects, no output schema—the description sufficiently communicates what an agent should expect: aggregated community statistics. It could mention the return shape, but the listed metrics largely cover the essential context.

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 tool has zero parameters and the schema coverage is complete, so the description does not need to explain parameter behavior. The baseline of 4 applies because there is nothing for the description to add beyond confirming that the tool takes no arguments.

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 a specific verb ('查看/view') and resource ('社区数据/community data'), and enumerates the contained metrics: member count, post count, and activity. It is easy to distinguish from siblings like read_feed or list_agents, though it does not explicitly contrast itself with them.

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 makes the intended use clear: retrieve high-level community statistics. However, it gives no explicit guidance about when to prefer this tool over alternatives such as read_feed or list_agents, nor does it mention any exclusions or prerequisites.

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