create_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. It only indicates a mutation (implying a write), but doesn't disclose side effects, return values, required permissions, or reversibility, leaving significant gaps for a write operation.

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 includes a long, truncated example JSON that seems auto-generated and isn't useful without further explanation. The opening phrase is brief, but the overall structure is cluttered and not front-loaded with the most essential information.

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 mutation with 10 parameters and no output schema, this description is severely insufficient. It doesn't explain what a role is, how creation works, or what the parameters are for, making it impossible for an agent to understand the tool's context or use 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?

Schema description coverage is 100%, so the baseline is 3. The description adds an example variable structure for filter and order, which provides some context beyond the schema's 'GraphQL: AccessGroupFilter' labels, but it doesn't explain the required 'input' parameter and is truncated, so extra meaning is limited.

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 reads 'Access Groups · mutation createRole', which essentially restates the tool name (create_role vs createRole) without offering an explicit statement of what the tool does or which resource it mutates. It doesn't differentiate the tool from siblings like create_access_group or update_role.

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?

No guidance is given about when to use this tool versus alternatives. It lists variables and an example but provides no context on prerequisites, use cases, or exclusions.

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