Contract Testing: Admin Create Role

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

The description only states 'Create a new role', which is already obvious from the name and annotations. Annotations already declare readOnlyHint=false (write operation) and destructiveHint=false (non-destructive). The description adds no additional behavioral context such as whether creation is idempotent, if it triggers side effects, or what the response contains.

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 concise, with a one-line summary followed by a bullet list of parameters. Every sentence is necessary. However, it could be more informative without becoming verbose.

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?

Given the low complexity (3 params, no output schema), the description is minimal but lacks crucial context such as that this is an admin operation requiring appropriate permissions, or whether roles are system-wide. It is barely adequate for an agent to understand the tool's use.

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 schema already documents all three parameters. The description repeats parameter names and types but does not add meaning beyond the schema. For example, it does not explain the format of 'name' or the valid values for 'permissions' scopes, which the schema already describes as 'e.g. webhook:read, user:manage'.

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 'Create a new role with specific permissions', which matches the tool's name and title. It distinguishes from siblings like update_role and delete_role by explicitly using 'Create'. However, it doesn't explicitly differentiate from other admin creation tools (e.g., create_team, create_user), but the focus on 'role' and 'permissions' makes it clear.

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 no guidance on when to use this tool versus alternatives like contract-testing_admin_update_role or contract-testing_admin_list_roles. There is no mention of prerequisites (e.g., admin privileges), nor any context about when not to use it. The toolset label 'Admin' is in the title but not in the description.

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