list-roles

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

With no annotations, the description must fully disclose behavioral traits. It states 'list all roles' implying a read operation, but fails to mention pagination, default filtering, maximum results, or response structure. The lack of detail on behavior like whether results are sorted or limited reduces transparency.

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 concise sentence that conveys the core functionality without fluff. It is front-loaded with the action and scope, making it easy to parse. Every word earns its place.

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 5 parameters, no output schema, and multiple sibling tools, the description lacks completeness. It omits details on pagination, default behavior, return type, and how filters interact. The agent is not equipped to use the tool fully based on this description alone.

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 coverage is 100%, so the baseline is 3. The description adds minimal value beyond the schema by listing filterable fields (status, department, active status), but 'status' does not match a parameter. It does not explain 'level' or 'per-page', which are in the schema, so no significant additional semantics.

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 all roles' with a specific verb and resource. It mentions optional filtering by status, department, or active status, which are mostly present in the schema (active and department_id). However, 'status' is not a parameter, causing minor confusion. It distinguishes from sibling tools like get-role but does not explicitly differentiate from other list-* tools.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., get-role for a single role, get-role-permissions for permissions). The description does not specify context or exclusions, leaving the agent to infer usage without support.

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