seerr_list_user

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

With readOnlyHint=true annotation, the agent knows it is a safe read. However, the description adds no behavioral details such as pagination behavior, sorting options, or that it returns a list. 'Get all users' is essentially the tool's label, not additional behavioral transparency beyond the annotation.

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 with no redundancy. It is front-loaded and easily understood. However, it may be too minimal, lacking elaboration that could fit without bloat. Still, for conciseness alone it earns a high score.

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's 6 parameters and lack of parameter descriptions in the schema, the description is severely incomplete. It does not mention pagination, filtering, sorting, or any response characteristics. The output schema exists but the description adds no context to help an agent fully utilize the tool.

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 0% and the description entirely fails to explain any of the 6 parameters (q, skip, sort, take, include_ids, sort_direction). The description 'Get all users' provides no semantic context for these parameters, leaving the agent without meaningful guidance on how to use them.

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 'Get all users' clearly identifies the action (get) and resource (users), distinguishing it from single-user tools like seerr_get_user. However, it is slightly ambiguous given the pagination parameters (skip, take) which suggest it may not return all users in one call. Still, the core purpose is clear.

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. There is no mention of prerequisites, or when to prefer this over seerr_get_user, user management tools, or other list tools. The description simply states the function without context.

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