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

With no annotations, the description takes on safety and side-effect disclosure. It warns that participant_secret is the only way to resume identity and must be persisted durably, and it notes the publish/replace behavior. It doesn't address failure modes or network visibility, but it covers the most critical behavioral facts.

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 tight sentences, front-loaded with the action, then the critical secret warning, then a one-line data-minimization rule. Nothing is redundant.

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?

For a tool with nested intent objects and no output schema, the description plus the fully annotated schema give an agent enough to call it correctly. It would be a 5 if it also described the response shape or common failure cases, but these aren't required for basic invocation.

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%, so the baseline is 3 even without extra parameter details in the description. The text adds only general guidance ('coarse routing facts') and doesn't need to expand on the already well-documented 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?

The description specifies two concrete actions — create or resume a network identity — and adds the ancillary publish/replace of matchmaking intent. This verb+resource framing clearly separates 'join' from siblings like discover or rendezvous_open.

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 when to call it (new identity or resuming existing) and gives operational guidance ('supply only coarse routing facts; keep rich personal context in your own memory'). It doesn't explicitly say when not to use it or point to alternatives, so not a 5.

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