list_roles

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

No annotations are provided, so the description must fully disclose behavioral traits. It only says 'List', which implies a read operation, but lacks details about idempotency, rate limits, ordering, or response format. Important behavioral context for a listing operation is missing.

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, clear sentence with no wasted words. Every word adds value: it specifies the resource, the action, and the capability (filters and pagination).

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?

Given the tool has 4 parameters and no output schema, the description is relatively concise but leaves out important details like how pagination works (e.g., use of 'page' and 'page_size') and whether the response includes total count. It is adequate for a simple listing but incomplete for nuanced usage.

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 description adds only 'optional filters and pagination', which vaguely hints at the parameters. With 50% schema coverage (two of four parameters lack descriptions), the description does not compensate by explaining the 'page' and 'page_size' parameters. The 'search' and 'type' parameters have schema descriptions, but the overall semantic value from the description is minimal.

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 explicitly states the action ('List') and the resource ('Logto API resource roles'), clearly distinguishing it from sibling tools like 'get_role' (single role) and 'list_user_roles' (user-specific roles). It's specific and immediately understandable.

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 mentions 'optional filters and pagination', giving a sense of usage context. However, it does not provide explicit guidance on when to use this tool versus alternatives (e.g., 'get_role' for a single role) or any constraints on filter usage.

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