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

With no annotations provided, the description carries the burden. The verb 'List' unambiguously indicates a read-only operation with no side effects. For a zero-parameter tool, this is sufficient behavioral disclosure, though it does not detail the structure of the returned list.

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, compact sentence that front-loads the action ('List') and the scope ('available roles/groups'), and includes the access level prefix. Every word adds value, with no redundancy.

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 zero-parameter listing tool without an output schema, the description clearly states what the tool returns (a list of roles) and who should use it (admins). No further details are necessary for the agent to select and invoke it correctly.

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 has zero parameters, so the description need not elaborate. The baseline score of 4 applies; the description contributes no parameter details because there are none to contribute.

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 uses the specific verb 'List' and identifies the resource as 'available roles/groups', with concrete examples (Admin, Lab Member, Curator). This clearly distinguishes it from sibling tools like create_role or assign_role, which are about mutation or assignment rather than enumeration.

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 '(Admin)' prefix provides a clear context that this is an administrative operation, implying only admin users should invoke it. However, it does not explicitly mention alternatives or when-not conditions, so the guidance is contextual rather than fully explicit.

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