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

The description goes well beyond the annotations by explaining key behaviors: grants are additive, revoking the last role removes the member from the roster, participants/team leads consume seats while staff do not, and the required scope (hack:admin). This provides critical context for a destructive operation and does not contradict the destructiveHint=true annotation.

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 dense but highly efficient. It front-loads the purpose, then adds behavioral context, then lists args and returns in a compact structure. Every clause adds value; no filler or repetition exists.

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 complex administrative tool with 7 parameters and no output schema, the description covers all essentials: purpose, argument semantics, behavior, return value, and required scope. It also notes edge cases (last role removal, seat consumption), making it complete for an agent to invoke 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?

With 0% schema description coverage, the description fully compensates by listing all 7 parameters and their optionality (eid?, display_name?, email?, org?), explaining the action enum, and describing the meaning of roles in the roster context. This makes the parameter semantics much clearer than the raw schema alone.

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 opens with a specific verb and resource: 'Grant or revoke event roles'. It clearly states the tool's function and distinguishes it from siblings like ic_hack_admin_decide_application (applications) and ic_hack_admin_phase (phase management). The specificity leaves no ambiguity about what this 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 provides strong contextual guidance: it explains that this is how judges, sponsors, mentors, and volunteers are admitted, including non-IC members via ext_ IDs. It also notes the additive nature and seat consumption rules. However, it does not explicitly mention alternative tools or when not to use this tool, so it falls short of a 5.

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