List realm roles

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

No annotations exist, so the description bears the full burden. 'List the realm-level roles' clarifies that this is a read-only operation and scopes the result to realm-level rather than client roles, which is useful context. It omits any note on potential pagination, authorization, or size details, but for a straightforward listing tool, this is adequate.

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?

A single concise sentence that starts with the main verb 'List' and directly names the resource. There is no filler, and the phrase 'realm-level' front-loads the key differentiator, making it easy to process.

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 is simple with only one required parameter and no output schema, so the description sufficiently indicates what the operation does. The only possible missing piece is an explicit statement about the return value, but for a basic list operation, the information provided is enough for a capable agent to invoke it confidently.

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 input schema already defines the only parameter, 'realm,' with 100% coverage and a 'Realm name' description, so the tool description adds little beyond implying that the realm is the one containing the roles. Baseline 3 applies because the schema handles the documentation, and the description offers no extra examples or behavior.

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 verb 'List' and the resource 'realm-level roles defined in a realm.' It differentiates from siblings like list_realms and list_users by explicitly naming the entity being listed, so an agent knows exactly what this tool is for.

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 purpose makes its usage implied: when you need the roles that exist at the realm level. However, it does not explicitly state when not to use it or which sibling alternatives (e.g., get_realm, list_realms) might be more appropriate in different scenarios, leaving the routing decision to the model.

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