umbrella_list_roles

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

The description makes the core behavior clear: a read-only enumeration of all available roles in the organization. However, with no annotations provided, it does not disclose potential details such as pagination, authentication requirements, or response shape. This is a minor gap for a simple zero-parameter list operation.

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, well-structured sentence with no filler. The action and resource are front-loaded, making it immediately scannable for an agent.

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?

For a tool with no input parameters, no output schema, and minimal side effects, the description is sufficiently complete for correct invocation. It identifies both what is returned and the organizational scope. Additional return-field details would be useful but are not necessary for basic selection and 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?

There are no parameters and the schema coverage is 100%, so there is no parameter-level ambiguity to resolve. The phrase 'all administrative roles' appropriately reinforces that no filters or inputs are needed.

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 names a specific action ('List') and a distinct resource ('administrative roles'), scoped to the Umbrella organization. It clearly differentiates this tool from sibling list tools such as umbrella_list_networks and umbrella_list_users.

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 intended use is clear and unambiguous: retrieve the complete set of administrative roles for the organization. It does not explicitly mention alternatives or exclusions, but the unique resource type and zero-parameter signature provide sufficient contextual guidance.

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