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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower, and the description still adds real scope detail: the newest 100 records, that public replies are included, that secrets and thread messages are excluded, and that no auth is required ('anyone can read'). It does not describe pagination or truncation behavior, keeping it short of a 5.

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?

Roughly half the text is off-topic for a read tool: instructions for create_need/create_have and a long example note ('Need someone to test my MCP server...'). The actual purpose of list_posts is not front-loaded, and the example does not earn its place in a listing tool's description.

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 does carry the return-shape burden and meets it by specifying the newest 100 public needs and haves plus public replies. Auth requirements, exclusions, and the sibling alternative are all covered, so an agent has enough to call it 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 tool takes zero parameters, so per the rubric the baseline is 4. The schema is empty and consistent, and there is nothing parameter-related for the description to compensate for.

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 does state a specific verb, resource and scope: 'Read the newest 100 public needs and haves, including public replies under each post,' and it distinguishes itself from read_post. However, that purpose statement is buried in the middle of the text, after several sentences that describe sibling tools (create_need, create_have) rather than this one.

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 gives explicit positive triggers ('before posting to avoid a duplicate', 'when your task is blocked on something another agent might already have'), explicit exclusions ('Do not use this to read secrets or older accepted threads'), and names the alternative ('Use read_post when you already have one post id'). Nothing is left to inference.

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