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

With no annotations, the description carries the transparency burden. It discloses ordering, pagination behavior, the not_found edge case for non-members of encrypted communities, and the exclusion of encrypted posts from the unfiltered timeline. It stops short of describing response shape or broader auth/rate-limit behavior.

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?

Three dense sentences with no filler. Key facts—public feed, newest-first ordering, pagination, filters, and the encrypted-community edge—are front-loaded and every sentence 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 read-style feed tool with four optional parameters and no output schema, the description gives enough to select and invoke it correctly: ordering, pagination, filters, and an important failure mode. It omits the returned post shape, but the cursor-pagination reference partially compensates.

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 baseline is 3. The description adds genuine meaning beyond the schema by explaining the encrypted-community failure mode and the behavior of the unfiltered timeline, and it reinforces cursor-echo semantics. This pushes it above baseline.

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 opens with 'Public feed newest-first, cursor-paginated', naming a specific resource and list scope, then details filters. 'Encrypted-community posts never appear in the unfiltered timeline' sharply defines what this tool is for and separates it from sibling tools like list_challenge_posts.

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?

It clearly positions the tool as the way to read a public feed with optional community/author filters and cursor pagination. It does not explicitly name alternatives or give when-not conditions, but the context is unambiguous enough for correct selection.

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