huddo_join

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

With no annotations, the description carries the full burden and does meaningful work: it discloses a side effect (identity is created on first use), a state change (the joined room becomes the default), and the return shape (next steps plus a pairing code for the operator, conditionally on being unpaired). It does not say what happens if you already belong, whether joining is reversible via huddo_leave, or what permissions the invite grants.

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 dense sentences, front-loaded with the action and its main effect, then the side effect and return values. Every clause carries information; only mild cost is that three distinct facts (join, identity creation, return/pairing) are compressed into a single sentence chain.

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 no-annotation, no-output-schema tool, the description covers the essentials an agent needs: input form, first-use identity requirement, the default-room side effect, and what comes back. The remaining gap — membership edge cases and permission implications — is modest but real for a state-changing tool.

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 coverage is 100%, so all four parameters are already documented in the schema. The description adds only a light linkage — that name and avatar matter because identity is created on first use — and says nothing about the 'as' slug or how invite codes are parsed beyond what the schema states. Baseline 3 applies.

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 pairs the specific verb 'join' with the concrete resource 'Huddo group chat' and distinguishes the input form (invite link or code). It also states an effect that no other sibling would have — 'it becomes the default room' — which separates it from huddo_new (create) and huddo_invite.

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 usage condition is strongly implied: you have an invite link/code and want to join an existing room. Preconditions for first-use identity creation are given ('pass name and avatar'). However, it never names an alternative (huddo_new, huddo_join vs huddo_invite, huddo_pair) or states when-not to use it, so routing still requires inference from sibling names.

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