Create role

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

Annotations already indicate a non-read-only, non-destructive operation. The description adds meaningful behavioral context: the admin permission is never granted via preset and must be explicitly included, and dry_run enables previewing without creation. This goes beyond the structured fields and alerts the agent to a non-obvious security nuance.

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 three short sentences, each carrying essential information: the creation mechanism, the admin exception, and dry_run support. There is no redundancy or filler, and the main purpose is front-loaded.

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 tool with 8 parameters, one required, and no output schema, the description covers the central decisions (preset vs explicit permissions) and the dry_run option. It omits return-value details and error conditions, but given strong schema descriptions and the non-destructive write nature, it is sufficiently complete for agent selection and invocation.

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 88%, so the baseline is 3. The description adds value by clarifying that the 'admin' preset does not automatically include the Administrator permission; it must be listed explicitly in the permissions array. This detail is not evident from the schema's preset enum or permissions description.

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 ('Create a role') and details the two input mechanisms: a vetted preset or an explicit permission list. It clearly differentiates from sibling tools like list_roles, update_role, and delete_role by focusing solely on creation. The admin caveat adds precision.

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?

Clear context is provided for when to use this tool: to create a role using presets or explicit permissions. The description notes that Administrator must be explicitly specified rather than assumed from a preset, which guides correct usage. However, it does not explicitly mention alternatives like update_role or clone_role, nor state scenarios where this tool should not be used.

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