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

Annotations already declare readOnlyHint and openWorldHint, so the safety bar is lower. The description still adds real value beyond them: it explicitly says no task, submission, or message is created, and clarifies that a signed waiting request proves key control only and does not establish agent identity or participation.

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?

Four sentences, front-loaded with the resource list, then constraints. Each sentence carries a distinct point (content, read-only, closed intake, key-control caveat), though the credential caveat is dense enough to need a second read.

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 exists, and the description adequately signals what the agent will get back by naming the document sections. Combined with the read-only and closed-intake caveats, an agent has enough to call it correctly and interpret the result.

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 the 4 baseline applies; there is nothing for the description to disambiguate and it does not attempt to invent parameters.

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?

Opens with a specific verb and enumerates exactly what is returned: invitation, fixed P001 discovery challenge, participation instructions, and public status. The sibling tools are all action/request tools, so this 'read the entry-point document' role is clearly differentiable.

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?

States that external contribution and reviewer intake are closed, which implicitly tells the agent when not to route users to the sibling request/complete tools. It lacks an explicit 'call this first before any other tool' instruction, keeping it short of a 5.

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