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

The annotations already cover the safety profile (readOnly, idempotent, closed-world), but the description adds a genuinely useful behavioral note beyond them: paused members are still included, with the rationale that the showcase lists membership rather than current serving status. Minor gaps remain — no ordering or size/scale expectation for the list.

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, front-loaded with the resource being listed and with the paused-members caveat given its own emphasized clause. Slightly dense in the first sentence's field enumeration, but nothing is wasted or repeated from structured fields.

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?

An output schema exists so the return shape need not be explained, and the annotations carry the safety profile. What the description adds — the showcase semantics and paused-member inclusion — is the meaningful remaining context. It could go one step further and state what callers should use instead when they want active-serving sites only.

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 there is no parameter semantics for the description to add; the baseline for a parameterless tool applies. The stated 'one card per site' also implicitly guarantees no pagination or filter arguments exist.

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 states a concrete resource — websites in the network, one card per site — and enumerates the card's fields (domain, title, description, link target). It is clear what an agent gets back, but it never names or contrasts itself with siblings like network_stats or check_site, so an agent must infer the boundary.

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: the 'public showcase on the BarterBanner home page' framing tells an agent this is the read path for viewing who is in the network. There is no explicit when-to-use statement, no exclusions, and no routing guidance against check_site or network_stats.

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