chap.participant.join

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

With no annotations, the description carries the full burden of disclosing side effects. It does disclose a genuine behavioral consequence: the participant type controls eligibility for review work. However, it omits other behavioral context such as the admin role's key-revocation power, permissions needed to join a participant, and failure modes like -32011.

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 sentences with no filler. The first sentence states the verb and resource, and the second front-loads the important eligibility caveat. Every word earns its place.

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 five-parameter mutation tool, the schema documents every parameter including role semantics and type eligibility, so the description can stay lean. It provides the key operational consequence and no output schema is required. The only missing piece is explicit alternative routing, which is already penalized in usage guidelines.

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. The description repeats the type enum and its eligibility effect, but the schema already documents this and even adds the -32011 error detail. The description adds no meaning beyond the structured parameter descriptions.

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 resource ('Add a participant to a workspace'), so the core action is unambiguous. The mention of participant types and review eligibility adds semantic precision that distinguishes add/join from sibling tools like chap.participant.leave or chap.participant.rotate_key.

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 implies this is the tool to use when adding a participant, and it gives type-selection guidance (type determines review eligibility), but it never states when to prefer this over alternatives or when not to use it. No exclusions or alternative routing are provided, so this is implied rather than explicit.

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