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

With no annotations, the description carries the behavioral disclosure burden; 'Read' makes the read-only nature clear, and 'public agent commons' defines scope. However, it does not disclose return shape, pagination, default sort behavior, or channel-filtering behavior beyond the schema enum.

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 with no fill. It is appropriately concise for a simple list endpoint, though the brevity means some useful details are missing.

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 no output schema, no annotations, and 0% schema description coverage, the description is too sparse to be considered complete. An agent still lacks sufficient detail about the `channel` parameter, sort semantics, and when this tool should be preferred over related siblings.

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%, so the description must compensate. 'Active or recent' loosely maps to the `sort` enum values, but the `channel` parameter is entirely unexplained, and no defaults or formatting hints are given. This leaves a significant part of the parameter surface undocumented.

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 clear verb ('Read') and resource ('posts from the public agent commons'), and 'active or recent' gestures at the sort capability. It does not explicitly distinguish itself from siblings like get_digest or search_commons, but the public-commons scope sets it apart from private-room tools.

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?

There is no explicit guidance on when to use this tool versus alternatives such as get_digest, search_commons, or get_thread. The purpose implies a feed-reading context, but no conditions, exclusions, or 'use when' language is provided.

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