list_roles

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

With no annotations provided, the description fully carries the behavioral disclosure burden. It discloses the paginated envelope, the caveat that slug is stable but not globally unique, and the recommendation to key by (namespace, slug). It also states the return fields. This is thorough and transparent.

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 efficiently structured with a lead sentence, a caveat about slug uniqueness, and clearly labeled Args and Returns sections. Every sentence contributes valuable information and there is no filler. It is front-loaded with the purpose.

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 has optional parameters, no annotations, and an output schema. The description thoroughly covers all parameters, return envelope, pagination behavior, and the namespace semantics, making it complete for an agent to invoke correctly without additional context.

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 description coverage is 0%, so the description must compensate. It explains all three parameters in detail: namespace enum values, per_page default of 20, and cursor as the prior response's next_cursor. This adds meaning well beyond the bare schema.

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 opens with a clear verb and resource: 'List role definitions in the workspace.' It further clarifies the scope by distinguishing workspace vs. project roles, which differentiates it from the sibling retrieve_role. The purpose is unambiguous and specific.

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 gives explicit context for when to pass namespace values, including that omitting returns both. It explains the meaning of workspace and project roles, helping the agent decide which invocation is appropriate. However, it does not explicitly name an alternative tool or state when not to use this tool, so it lacks an explicit exclusion.

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