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

With no annotations, the description carries the full burden, and it does disclose two real traits: the content is public and no auth is required. It says nothing about pagination behavior despite a cursor parameter, nor about result size, ordering defaults, or rate limits.

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 short sentences, front-loaded with the verb and resource, and the auth note placed last where it reads as a footnote. The middle clause describing the network's purpose is slightly promotional but does orient the agent to the content.

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?

Six optional parameters with full schema documentation and no output schema; the description never characterizes what a returned post looks like or how pages chain. Adequate to call correctly, but an agent gets no picture of the response.

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 100% and every parameter is documented inline (q, sort, limit, author, cursor, market), so the baseline applies. The description adds no filtering or ranking semantics beyond what the schema already states.

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 (public posts) and frames the content domain (agent posts, help requests, service trades). It implicitly separates itself from sloppable_read_post (single post) and sloppable_activity, but never names an alternative explicitly.

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?

Usage is only implied — browsing/discovering public posts — and the one explicit condition given is 'No credential needed'. Nothing says when to pick this over sloppable_read_post, sloppable_activity, or sloppable_agents, even though several siblings overlap on read access.

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