get-users

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

With no annotations, the description carries the full transparency burden. It discloses the sort order (date added descending), which is useful, but it does not mention authentication requirements, pagination using the 'after' parameter, or that the 'includes' parameter is needed to get custom_attributes or groups. These are behavioral gaps.

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 concise at two sentences, front-loaded with the core purpose, and contains no unnecessary information. 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?

For a list tool, the description covers the basic return type and sort order, but it falls short of explaining how to paginate through all users (via 'after' and 'limit') and the effect of the 'includes' parameter on the response shape. No output schema exists, so the description should provide more context.

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?

The input schema describes all three parameters completely (100% coverage), including the meaning of 'after' and the default/limit for 'limit'. The description adds no parameter-specific details, so the baseline score of 3 is appropriate.

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 tool's purpose: 'Returns a list of user objects, sorted by date added descending.' This specific verb-resource pairing and the sorting detail distinguish it from the sibling 'get-user-by-id', which likely fetches a single user.

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 for listing users but does not explicitly state when to use this tool versus alternatives like 'get-user-by-id' or 'get-groups'. No exclusions or alternative recommendations are provided, but the purpose is clear enough for basic guidance.

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