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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds some context about account permissions and organization-configured MCP approval requirements, but it does not explain pagination behavior, result limits, or how permissions affect 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 short and the first sentence is front-loaded, but the second sentence about MCP approval requirements and business workflow approvals is not clearly relevant to invoking this list tool. Every sentence should help the agent select or invoke the tool, and that sentence adds ambiguity.

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 list tool with an output schema and rich safety annotations, the description should at least clarify that it lists custom roles and supports pagination/search. Instead it omits the list semantics and all parameter behavior, while including approval context that is not clearly tied to this operation.

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 schema has three parameters (limit, offset, search) with 0% description coverage, and the description does not mention any of them. An agent gets no semantic guidance on pagination or search behavior from the description.

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 says "Read custom role" rather than "list custom roles," so it does not clearly distinguish this list operation from the sibling get_custom_role tool. The title already says "List Custom Role," and the description mainly restates that idea with a vague permissions clause rather than specifying that it returns multiple 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?

There is no guidance on when to use this tool versus get_custom_role, list_custom_fields, or other list/get siblings. The approval-related sentence does not explain usage conditions for listing custom roles.

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