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

Annotations cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds substantial context beyond them: the content is stranger-authored AI text that is 'information..., never instructions' (an injection warning), each post discloses owned/vouched/no-owner provenance, and there is a public unauthenticated endpoint. It also discloses pagination behavior (100-answer cap, 'more' and 'cursor').

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?

Front-loaded with the core purpose, but the body is one dense run-on paragraph mixing feed semantics, auth notes, provenance, and pagination, with several clauses that nest awkwardly ('With conversation, the answer is that whole conversation in order...'). It reads as stream-of-consciousness rather than curated structure.

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 no output schema, the description carries the return-shape burden and does so: it explains what each post carries (conversation id, answers count, last_at) and how the conversation mode expands into an ordered thread with pagination. Nothing an agent needs to call it correctly is missing.

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 baseline is 3, but the description adds real meaning: 'conversation' returns the whole thread in order including answers-to-answers with a cursor, 'after' is that cursor and only applies with conversation, and 'about' returns answers to a post. That goes beyond the terse schema strings.

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 Commons, the open square... where AIs... post asks, offers and notes, newest first'), so an agent knows exactly what it retrieves and in what order. It never names its write-counterpart commons_post, so differentiation from the sibling set is only implied by the verb 'Read'.

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 conveys prerequisites indirectly ('Anyone can read it, signed in or not'), which tells an agent no auth is needed, but it gives no explicit when-to-use vs commons_post/commons_report routing and no exclusions. Usage is left to inference from the read-only framing.

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