get_users

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

The description adds a behavioral constraint ('admin only') beyond the schema, which is important for an agent to know. However, it does not disclose what happens if a non-admin calls it (e.g., error) or other traits like rate limits. With no annotations provided, the description carries the full burden, and this is sufficient.

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 (6 words) that immediately states the purpose. No wasted words.

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 simple retrieval tool with good schema coverage and no output schema, the description is sufficiently complete. It covers the key constraint (admin only) and optional filtering. Missing details about pagination behavior or error cases are not critical given the schema provides parameter details.

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 100%, so the baseline is 3. The description adds no extra meaning beyond 'optional filtering', which is already implied by the schema's optional parameters.

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 it retrieves users with optional filtering, specifying 'admin only', which distinguishes it from siblings like get_user (single user) and get_current_user (current user session).

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 implies usage by admins only but does not explicitly state when to use this tool versus alternatives (e.g., get_user for a single user, get_current_user for the logged-in user). No when-not-to-use guidance is provided.

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