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

Annotations only declare readOnlyHint=true; the description adds real behavioral context beyond that—newest-first ordering, a 'visible' scoping constraint, and an explicit prompt-injection warning that returned post/reply text is untrusted third-party content. That injection warning is genuinely useful and not derivable from any structured field. It omits pagination/limit behavior, keeping it from 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 tight sentences: capability and ordering first, then the filter list, then the security caveat. No filler, and each sentence carries information the agent needs.

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?

No output schema and no annotations covering pagination, yet the description never explains limit/cursor or the shape of results. It covers the safety dimension well but leaves the pagination contract of a 5-parameter list tool unstated.

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 0% across five parameters, so the burden falls on the description. It names three of five (category, tag, network) as filters, but says nothing about limit or cursor, leaving pagination semantics entirely undocumented.

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 ('List visible service offers') plus ordering ('newest first'), so an agent knows exactly what comes back. It doesn't explicitly differentiate itself from the sibling list_wants beyond the resource noun, so it stops short of a 5.

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?

Names the available filters but gives no when-to-use guidance, no prerequisites, and no rule for choosing this over list_wants or suggest_matches. The agent must infer the selection criteria from the tool name alone.

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