get_realm_role_composites

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

No annotations are provided, and the description does not disclose any behavioral traits such as idempotency, authentication requirements, or read-only nature. As a get operation, it is likely safe, but this is not explicitly stated.

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 extremely concise but lacks necessary specificity. While brevity is generally good, the single phrase 'Get composites of a realm role' is too terse and fails to distinguish from sibling tools or provide any structural guidance.

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 the absence of annotations and output schema, the description should compensate with more detail. The two-parameter tool is minimally described, but the ambiguity with sibling tools and lack of output information makes it insufficient for reliable usage.

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?

Both parameters have descriptions in the schema ('Realm name', 'Role name') that sufficiently explain their meaning. The description adds no additional semantic context, but schema coverage is high (100%), so a baseline of 3 is appropriate.

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 'Get composites of a realm role' is clear on a basic level but vague: it doesn't specify whether these are client composites, realm composites, or both. Sibling tools like 'get_realm_role_client_composites' and 'get_realm_role_realm_composites' are more specific, creating ambiguity about the exact output.

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 offers no guidance on when to use this tool versus more specific siblings. Without context, an agent may not know if it should use this tool for all composites or prefer the specialized ones.

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