Create Role

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

Annotations already indicate readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the description's extra context about role-based sharing and hierarchy is additive value. It explains the semantic consequences of roles without contradicting annotations. There is no mention of return values or side effects, but the annotations cover the safety profile.

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?

Three concise sentences: the first states the action, the second explains the domain concept, and the third gives a key parameter guidance. No filler or repetition. The description is front-loaded with the purpose and earns its length.

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 tool has 9 parameters and no output schema, so some return-value guidance could be useful. The description explains core hierarchy behavior and parent role placement, covering the most critical context. The absence of response details is a mild gap, but the description adequately frames the tool's operation for an agent.

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?

With 100% schema description coverage, the baseline is 3. The description adds value by explaining the parentRole parameter's role in placing the role in the hierarchy, which directly ties to record visibility. It also implies the access-level parameters affect subordinate visibility, though it doesn't detail syntax. This exceeds the baseline by connecting parameters to their business 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 opens with 'Creates a Role in the Salesforce role hierarchy,' which is a specific verb-resource pairing. It clarifies the domain (role hierarchy) and distinguishes this from sibling tools like sf_create_role_hierarchy or sf_create_user_role_hierarchy by focusing on a single Role entity. The contextual statement about role-based sharing reinforces its unique purpose.

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 context on when to use the tool: when modeling a role hierarchy with record visibility implications. It explains the parentRole behavior and how to create a top-level role. However, it does not explicitly cite alternative tools or state when not to use this tool, so it falls short of a 5.

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