get_user_realm_roles

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

No annotations provided, so the description carries the full burden. It accurately describes a read operation with parameter details (e.g., effective for composite roles), but does not disclose behavior like error handling or side effects. Basic transparency with no contradictions.

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 concise at 7 lines, covering purpose, parameters, and return value. It avoids unnecessary detail but could be better structured (e.g., separate sections). No redundant content.

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 simple retrieval tool with an output schema (not shown), the description is adequate. It states the return type as a list of realm roles but lacks details on potential filters or error cases. Meets minimum viability.

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?

Schema coverage is 0%, so the description adds meaning beyond the schema. For example, it explains that 'effective' retrieves composite roles, which is not apparent from the schema. This compensates for the lack of schema descriptions.

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 it retrieves realm roles for a user, specifying parameters like user_id, effective, and realm. It distinguishes from siblings such as 'get_realm_role' (single role) and 'list_realm_roles' (all roles) by focusing on user-specific roles.

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?

No explicit guidance on when to use this tool versus alternatives like 'get_realm_role' or 'list_realm_roles'. The description lists arguments but lacks context on prerequisites or exclusions.

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