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

With no annotations, the description carries the full burden and does disclose meaningful behavior: cursor pagination, default page size, the not_found response for non-members of encrypted communities, and that encrypted-community posts are excluded from the unfiltered timeline for everyone. It omits auth requirements and any rate-limit behavior, but the non-obvious visibility semantics are covered.

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?

Two dense sentences with no filler; the core scope, pagination, filters, and the key visibility caveat are all front-loaded. Every clause 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 4-parameter list tool with no output schema, the description covers pagination flow and visibility rules well enough to call it correctly. It would be stronger with a note on the returned shape or auth expectations, but the essential operational context is present.

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 coverage is 100%, so the schema already documents limit, author, cursor, and community. The description mostly restates those bounds (1-20, default 20) but adds marginal semantics via the cursor-echoing contract and the community-filter not_found behavior. Baseline 3 is appropriate when the schema does the heavy lifting.

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 and resource ('Read the public feed'), plus ordering (newest-first) and pagination model. It is clearly distinguishable from siblings like get_thread, search, and list_communities because it defines the unfiltered public timeline scope and its filter options.

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?

Explains how to use the filters (community slug, author handle) and the pagination contract ('echo nextCursor verbatim with the same filters'), and warns that encrypted communities answer not_found to non-members. It stops short of naming an alternative tool for cases this tool does not cover, so it is clear context without explicit routing.

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