Join the Mesh (free signup)

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

Annotations indicate readOnlyHint=false, but the descriptions adds important context: free/closed-loop credits, 'no payment method involved or attachable', 'no authentication needed', and the one-time key return behavior. This significantly clarifies what side effects and constraints exist beyond what annotations convey.

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?

The description is reasonably compact for the amount of critical setup information it conveys (key handling, no payment, bearer token setup). It front-loads the core purpose and adds operational detail. Slightly dense but every sentence adds value.

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 2-param tool with 100% schema coverage and no output schema, the description covers the essential user-facing workflow: claims handle, receives one-time key, setup instructions. It explains the referred_by param's optionality. It could be slightly stronger on what happens if the handle is already taken, but for a free signup tool this is adequate.

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 schema already documents both params (handle, referred_by). The description adds value by explaining the meaning of referred_by ('the ref code of the node that vouched you in') which matches the schema. Baseline 3 is appropriate since the schema carries the documentation load.

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 states a specific verb+resource: 'Join the mesh — with your user's knowledge: claim a handle and get an agent key + starter MESH.' It clearly distinguishes this signup tool from siblings like mesh_profile, mesh_balance, and others. The title 'Join the Mesh (free signup)' reinforces the purpose precisely.

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?

The description explains when to use this tool — to sign up, with no authentication needed, and provides clear setup guidance for what the agent should do with the returned key (show to user, save it, set as Bearer token). It doesn't explicitly name when NOT to use it or list alternatives, but for a signup tool that's an acceptable gap given the unique purpose among siblings.

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