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

readOnlyHint=true already declares the safe-read profile, so the description doesn't need to restate it. It adds the endpoint (GET /roles) and the shape of the returned records, which is mild extra context, but says nothing about pagination behavior or how deleted roles appear even though include_deleted exists.

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?

Two compact sentences, zero filler, with the core purpose and returned fields front-loaded before the endpoint. Nothing is repeated from the title or schema.

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 filtered list tool with no output schema and annotations covering safety, the description is largely sufficient: purpose, returned fields, and endpoint are covered, and pagination is handled by the schema. It could be marginally improved by clarifying include_deleted behavior, but no critical gap remains.

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 100%, so all four parameters (ids, limit, offset, include_deleted) are already fully documented in the schema, including pagination semantics and the next_offset convention. The description adds no parameter-level meaning beyond that; baseline 3 applies.

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?

States a specific verb ('List') and resource ('job roles (positions)'), and the parenthetical disambiguates roles-as-positions from any permission/account role concept among the many list_* siblings. It also names the key fields returned (colour, default break, pay rate), so an agent knows exactly what it retrieves.

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 no when-to-use or when-not-to-use guidance and does not mention alternatives or prerequisites. Nothing tells the agent when to reach for this rather than rotacloud_list_users or rotacloud_get_user, beyond the obvious resource name.

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