list_users

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

No annotations are provided, so the description carries the full burden. It discloses ordering (most recent first) and pagination behavior (bounded page, not full table), which is useful. However, it omits the response structure (fields returned), filtering semantics beyond the schema, and any side effects or auth requirements. The disclosure is incomplete for a tool with no annotations.

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?

Two sentences with no fluff. The primary purpose is front-loaded, and the pagination caveat is stated concisely. 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?

Given 5 parameters and no output schema, the description is sparse. It does not describe the shape of returned user objects, default values, or how query/active/department affect results. While the list operation is simple, the lack of output schema and low parameter coverage leaves gaps that a more thorough description could fill.

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 only 20% (only 'query' has a description). The description adds meaning to limit/offset by explaining their role in pagination, but does not comment on 'active' or 'department' parameters. Since coverage is low, the description should compensate but only partially does, leaving two parameters semantically opaque.

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 'List users, most recent first' – a specific verb and resource with ordering. It distinguishes from the sibling get_user by plurality and from create_user/update_user by verb. The pagination note adds precision about the scope of the operation.

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 use for paginated listing by explaining limit/offset behavior and that it returns a bounded page. However, it does not explicitly state when to prefer this over get_user (single user) or how to combine with filters. No exclusion guidance is given, so the usage context is only partially conveyed.

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