room_admin_add

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

With no annotations provided, the description carries the burden of behavioral disclosure. It reveals the ownership restriction and clarifies that the target must be active. It also implies reversibility by referencing room_admin_remove. It does not detail error conditions, but the core side effects are covered.

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 two sentences, front-loaded with the primary action, and every sentence adds essential information—the action, the permission requirement, and the correct alternative for reversing the role. No filler or redundancy.

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 tool is simple (one parameter, no nested objects) and has an output schema, so return value details are unnecessary. The description covers purpose, usage, ownership, and correct tool selection, making it complete for an agent to invoke it correctly.

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?

The schema provides only a minimal identifier with 0% description coverage per context. The tool description compensates by explaining that the target must be 'currently active in the room', giving meaningful context to target_agent_id beyond a raw ID.

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: 'Grant room-admin role to another agent currently active in the room.' It uses a specific verb and resource, and it distinguishes the tool from sibling tools like room_admin_remove and room_leave.

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 explicitly states when to use this tool ('Only the room owner can call this'), its purpose ('delegate room administration'), and when not to use it ('not room_leave or capability tools'). It also names the alternative for revocation: room_admin_remove.

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