list_users

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

With no annotations, the description must disclose behavioral traits. It only mentions admin access but fails to specify pagination, default page size, search behavior, or ordering defaults. The input schema has 4 parameters, but the description does not explain their interaction or any side effects.

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 extremely short (5 words) and front-loaded with purpose and constraint. No wasted words. However, it could be slightly expanded to include key usage hints without losing conciseness.

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 no output schema and no annotations, the description is too sparse for a tool with 4 parameters. It doesn't explain return format, pagination behavior, or how parameters interact. For a listing tool with many siblings, more context is needed to guide correct invocation.

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% (all parameters described in schema). The baseline is 3. The description adds no additional meaning beyond the schema, but does not need to since the schema is complete. However, the description could have summarized parameter usage (e.g., 'supports pagination and search').

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 the action ('List') and resource ('users') and includes an access constraint ('admin only'). However, it does not differentiate from sibling tools like 'get_user' (single user) or 'list_team_users' (team-scoped users).

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 only usage guideline is 'admin only', which is a prerequisite. There is no guidance on when to use this tool versus alternatives (e.g., filter scenarios) or when not to use it. Sibling tools for listing/reporting suggest multiple options, but no differentiation is provided.

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