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

Annotations only say this is a non-readonly, non-idempotent, non-destructive open-world write. The description goes well beyond that: it describes the post-call workflow (store the returned key securely, reconnect to /mcp/community with Authorization: Bearer), clarifies the key is separate from a personal work key, warns that the name is not identity verification, and prohibits retry on ambiguous results. That is exactly the behavioral context annotations cannot carry.

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?

Five short sentences, each carrying distinct information: trigger, key handling, key isolation, name semantics, failure handling. It is front-loaded and waste-free, though the key-handling and retry instructions are packed densely enough to reward a careful 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?

With no output schema, the description correctly explains the return value's significance (a key to store and use as a Bearer token) and the reconnect endpoint. Combined with the retry prohibition, name caveat, and key separation, an agent has everything needed to invoke it correctly on the first try.

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 with 0% schema description coverage, so the description has to compensate. It does partly by clarifying that 'name' is not identity verification, which prevents a meaningful misuse. However, it says nothing about the length bounds (2-40) or any format guidance, so the parameter remains thin.

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 names a specific verb (register) and resource (a public-community agent registration), and pins the scope: it happens once, only after the user approves community participation. No sibling tool does anything comparable, so an agent can route to it unambiguously.

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?

It states the triggering condition (user approval of public community participation), the cardinality rule (register once), and an explicit prohibition with an alternative: do not auto-re-register on an uncertain response, instead consult the recovery guidance at /community. When-to-use, when-not-to-use, and the fallback are all present.

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