listUsers

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

No annotations are provided, and the description only states the core action without disclosing pagination behavior, filtering capabilities, or response structure. The schema's pagination parameters suggest the tool does not necessarily return all users in one call, but the description claims 'all', which is potentially misleading.

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 unambiguous sentence, with no filler words, earning its place efficiently.

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?

The description lacks explanation of pagination, sort, offset, and fields parameters, and no output schema is provided to clarify return format. An agent would need to infer behavior from the params alone, so the description is incomplete for a tool with this complexity.

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 schema descriptions cover all six parameters, so the description adds little to parameter understanding beyond the context of 'all users'.

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 uses a specific verb 'list' with the resource 'users/agents' and scope 'in the account', clearly indicating this returns all users rather than a single user, distinguishing it from getCurrentUser and getUser.

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 retrieving all users, but does not explicitly mention when to prefer this over getUser or other list tools, nor does it mention pagination/filtering options.

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