roles

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

With no annotations, the description must disclose behavior, but it only says 'query roles' and lists variable names. It does not explain pagination behavior, return shape, filtering semantics, or any side effects (likely none). The example provides some shape but is truncated and not explanatory.

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 text is short and front-loaded, but the example JSON is long, truncated mid-object, and not formatted for easy scanning. It is concise but the incomplete example hurts clarity.

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 tool with 6 parameters, no output schema, and no annotations, the description is insufficiently complete. It does not describe the return value, which is a list of roles, nor the meaning of 'after'/'first' for pagination, or the structure of order. The example partially compensates but is incomplete.

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 descriptions cover 100% of parameters, so baseline is 3. The description adds an example showing the structure of filter/notFilter, which gives some extra meaning beyond 'GraphQL: RoleFilter', but does not explain each parameter or value formats.

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 states 'query roles' which is a specific verb+resource, clearly indicating this tool lists/queries role objects. The plural 'roles' distinguishes it from sibling 'role' (singular) which likely fetches a single role, though not explicitly contrasted.

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 explicit guidance on when to use this tool versus alternatives like 'role' or 'create_role'. The example variables imply usage for filtering/pagination but there is no stated context or exclusions, leaving the agent to infer suitability.

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