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

No annotations are provided, so the description carries the full behavioral burden. It usefully signals that results are cached (potentially stale) and non-authoritative, but says nothing about freshness/TTL, how to refresh via the refresh_host* siblings, auth requirements, or failure behavior. For a tool with zero annotation coverage this leaves most behavior undisclosed.

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 short, front-loaded sentences with no filler; the cached-scope fact leads and the caveat follows. It is efficient, though the extreme brevity is part of the completeness problem rather than the fix.

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 annotations, no output schema, and an opaque concept ('participation', 'evidence'), the description is too thin to tell an agent what it will receive or when the result is trustworthy. It should at minimum define participation, characterize the evidence payload, and point to the refresh path for stale cache.

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 100% and the single 'domain' parameter is exhaustively documented in the schema (normalization, label rules, rejections), so the baseline of 3 applies. The description adds no additional meaning about how the domain relates to participation lookup, but it is not required to.

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 is essentially a restatement of the tool name ('participation status') with a caching modifier, and never defines what 'participation' means in this system. It gives no verb (retrieve? verify?) and no way to tell it apart from siblings like payto_check, verify_receipt, or lookup_host. It edges above a pure tautology only because of the 'Cached' scope qualifier and the disclaimer.

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 statement of when to call this versus alternatives, no prerequisites, and no mention of the refresh_host siblings that would clearly relate to a cached result. 'Not a legal finding' is an interpretation caveat, not usage guidance, so nothing routes the agent to this tool over its neighbors.

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