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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds that the tool lists and filters 'all your roles' and defines a role, which is some behavioral context. It does not disclose pagination behavior, return format, or rate limits, but given annotations cover the safety profile, this is acceptable.

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, using two sentences. However, the first sentence repeats 'List' ('List roles - List and filter...'), which is a minor redundancy. The second sentence about role definition is helpful but could be seen as extra. Overall, it is well-structured and front-loaded with the main 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?

Despite having 9 parameters and no output schema, the description provides minimal context. It does not explain filtering options, pagination, or expected return value. The annotations cover safety, but the tool has many parameters and the description leaves the agent without guidance on how to use filters or interpret results. This is a significant gap for a list tool with rich filtering capabilities.

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 9 parameters with zero description coverage, and the description does not compensate. It mentions 'filter' generically but does not explain any of the parameters (name, page, size, type, apiName, orderBy, tagName, x-request-id, x-trace-id). With complete lack of parameter guidance, the description fails to add meaning beyond the 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 clearly states 'List roles - List and filter all your roles' which indicates a specific verb (list/filter), resource (roles), and scope (all your roles). It distinguishes from sibling tools like retrieveRole, createRole, and deleteRole by focusing on the list operation. The additional explanation of what a role is adds useful context.

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 implies usage for listing and filtering roles, which is clear context. However, it does not explicitly mention alternatives or when not to use this tool. For instance, it doesn't say 'use retrieveRole for a single role' or mention any prerequisites. The context is clear but lacks explicit exclusions or comparisons to siblings.

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