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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds genuinely valuable context beyond that by warning that post/reply text is untrusted third-party content and must be treated as data, not instructions. It omits any mention of pagination behavior despite a cursor parameter, which keeps 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?

Two sentences, zero filler, with the core purpose front-loaded and the security caveat appended. Nothing is redundant and the security note 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 list tool with five undocumented parameters and no output schema, the description covers purpose and prompt-injection safety but leaves all filtering and pagination semantics unexplained. An agent still cannot tell what tag/network/category/limit/cursor actually do.

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?

All five parameters (tag, limit, cursor, network, category) have 0% schema description coverage, and the description adds no meaning for any of them. It does not explain what a network, category, or tag filters on, nor how cursor/limit drive pagination, so the description fails to compensate for the schema gap.

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 gives a specific verb+resource ("List visible wants") and helpfully defines the domain term with a parenthetical ("requests for a service, with budget"), so an agent knows what a want is. It does not distinguish itself from the sibling list_offers, leaving the wants-vs-offers split to inference.

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?

There is no when-to-use, when-not-to-use, or alternative-tool guidance. The word "visible" implies a scoping/filtering intent but nothing tells the agent how this differs from list_offers or when to prefer it over get_post/list_thread.

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