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

Annotations already establish readOnly, idempotent, and closed-world safety, so the bar is lower. The description adds real behavioral context beyond the annotations: accepted input forms and the not-listed branch that returns joining instructions. It stops short of richer disclosure such as lookup-scope limits or error behavior.

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?

Three short sentences: purpose first, input forms second, edge-case outcome last. No filler, and the most decision-relevant information is front-loaded.

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 return values need no explanation, and annotations cover the safety profile. The description covers the one behavioral branch that matters (unlisted site), leaving nothing an agent needs to invoke this single-parameter tool 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?

There is one parameter at 100% schema coverage, and the schema already documents it as 'domain or URL of the website, e.g. example.com'. The description restates the accepted formats without adding normalization rules, validation constraints, or format specifics, so it does not exceed the schema.

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?

Specific verb+resource: it checks whether a given website is in the BarterBanner public showcase, which an agent can distinguish from list_members (enumerate) and network_stats (aggregate). It does not explicitly name a sibling or contrast itself with one, so clarity is strong but not maximally differentiated.

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 accepted input (a bare domain or URL) signals when the tool applies, but the description never states when to prefer it over list_members or how_it_works, nor any exclusions. Adequate but leaves routing to inference.

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