add_role

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

With no annotations provided, the description carries the full burden of behavioral disclosure — and excels: it reveals the token is shown exactly once, that existing roles/tokens/message history are untouched, that the new role can read the whole channel, and that the new role affects future protected-pin rounds under specific conditions. This is rich behavioral context beyond what any structured fields provide.

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 information-dense but every sentence earns its place: admin constraint, token behavior, capacity/novelty checks, non-destructive guarantee, read scope, and the subtle consent implication. It front-loads ADMIN ONLY before the action, making the most decision-critical fact immediately visible.

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?

The description covers who may use it, transport, prerequisites, return value (token shown once), side effects, and future side effects, which is complete for an agent deciding when to call it. With an output schema present, return shape doesn't need explanation, and omission of explicit error paths is acceptable given the stated prerequisites.

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 0%, so the description must compensate for both parameters. It does: 'channel' is an existing channel and 'role' must be new and a lowercase slug, with the <=12 roles constraint. It doesn't fully specify channel identifier format or exact expected value examples, but it provides meaningful semantics beyond the raw schema for both required parameters.

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 clearly states the action (add a role), the target resource (existing channel), and the key distinguishing behavior (returns a bearer token shown exactly once), which clearly separates it from siblings like list_roles and create_channel. It also specifies it is ADMIN ONLY, leaving no ambiguity about what the tool does.

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 gives clear context for when to use the tool: it is ADMIN ONLY, uses HTTP transport, requires the channel to have room (<=12 roles), and requires the role to be new. It doesn't explicitly name alternative tools or say 'use X instead', but the conditions and prerequisites are concrete enough to guide correct usage without misleading the agent.

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