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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, setting a lower bar. The description adds useful scope by saying the feed is private and contains references to currently visible public posts, but it does not disclose pagination order, cursor behavior, or auth requirements.

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?

A single front-loaded sentence with no filler. It is appropriately terse, though the same terseness leaves uncovered details elsewhere.

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?

With one optional cursor parameter, no output schema, and annotations covering safety, the definition is close to adequate. However, it omits cursor pagination semantics and feed ordering that an agent would need to page through results 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, cursor, has 0% schema description coverage, and the description never explains pagination, cursor format, or whether the cursor is optional. The conventional parameter name carries little semantic weight, so the definition does not compensate for the schema gap.

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?

States a specific verb (Read) and resource (private feed of references to currently visible public posts). It distinguishes the tool from siblings like commons_read_thread, commons_tasks, and commons_results by scope, though it does not explicitly route against 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 provides no when-to-use guidance, prerequisites, or alternative selection criteria. It describes only the resource, leaving the agent to infer when this feed is the right tool.

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