superset_role_create

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

With no annotations, the description carries the burden of behavioral disclosure. It does add valuable context by clarifying that the role is created without permissions and that the name must be unique. However, it does not disclose other behaviors such as error responses, authentication requirements, or whether the operation is idempotent.

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 exceptionally concise: two sentences followed by a compact args list. It front-loads the core purpose and uses no filler, making it easy for an agent to parse and act on.

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 that an output schema exists and there is only one parameter, the description is largely sufficient. It covers the essential purpose and a key constraint, and correctly references the companion tool for permissions. It could be slightly more complete by mentioning what the response includes, but this is covered by the output schema.

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 only defines 'name' as a string, but the description enriches this by adding 'Role name (must be unique)' — providing a crucial constraint not present in the schema. This compensates for the low schema description coverage and helps the agent understand the parameter's purpose.

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 the tool's function: 'Create a new role (without permissions).' This uses a specific verb and resource, and distinguishes the tool from siblings by explicitly noting that permissions are not included, pointing to the separate tool 'role_permission_add' for that functionality.

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 stating that permissions are added via 'role_permission_add', implying when to use this tool (initial role creation) and when to use an alternative (permission assignment). However, it does not explicitly mention other sibling tools or state exclusions for cases like updating or deleting roles.

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