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

No annotations are provided, so the description carries the behavioral burden. It adds value by disclosing the cost (10 tokens), the return value (new role summary), and the connection-selection behavior. It does not discuss failure modes or permissions, but the mutation is implied by 'Create' and the extra details go beyond the structured data.

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?

Four terse, purposeful sentences: purpose, prerequisite/connection instruction, return value, and cost. Nothing is redundant or wasted, and the most important information 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?

The description provides the essential operational context: prerequisite call, default vs. targeted connection, return summary, and cost. Combined with the full schema coverage and output schema, this is sufficiently complete for reliable invocation, though error/duplicate-key behavior is not mentioned.

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?

The schema already provides 100% description coverage for all six parameters, so the baseline is 3. The description only restates the clerk_instance_id behavior already present in the schema, adding no new parameter-level meaning.

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 uses a specific verb ('Create') and resource ('new organization role in a connected Clerk application'), making the tool's function unmistakable. It also clearly distinguishes this from sibling tools like create_organization_permission and update_organization_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?

It explicitly states a prerequisite: 'Call clerk.get_connected_accounts first.' It also clarifies how to target a specific connection vs. the default account. It does not enumerate alternatives, but the usage context is clear enough for an agent to execute correctly.

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