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

The annotations declare readOnlyHint=true and idempotentHint=true, but the description claims a create operation, which is a mutation. This is a direct contradiction, making the behavioral profile misleading. The description does not resolve the contradiction and provides no additional clarity about side effects.

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 a single, front-loaded sentence that includes all key constraints. Every part earns its place, with no redundant or extraneous text.

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 schema covers parameter details well, but the description lacks any mention of the permissions parameter's effect or the broader role-creation context. The annotation contradiction further reduces completeness, as the agent cannot trust whether this is a safe read or a mutation. It is minimally viable but with clear gaps.

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%; all four parameters have meaningful descriptions. The description reinforces the priority rule (defaults and required priority threshold) but adds little beyond what the schema already provides. Therefore it meets the baseline for high coverage but does not compensate further.

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 states a specific action: 'Create a custom faction role'. The verb 'create' and the resource 'faction role' are clear and distinguish it from sibling tools like faction_edit_role and faction_delete_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?

The description provides clear usage context by specifying the required `manage_roles` permission and the priority constraint (2-99, must exceed new role's priority). It does not explicitly mention when not to use the tool or name alternatives, but the prerequisites are clearly stated.

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