list_users

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains pagination via offset and limit, and notes the return type (JSON array with metadata). It does not disclose permissions, rate limits, or any filtering constraints, which are relevant but not critical for a simple read operation.

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 well-structured: a one-line summary, a clarifying sentence, then Args, Returns, and Examples. Each section serves a purpose and is front-loaded with the main functionality. No superfluous text.

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 straightforward list tool with two pagination parameters, the description covers purpose, parameter semantics, return type, and usage examples. The existence of an output schema reduces the need to detail return structure, and the description provides enough context for 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?

The schema has zero descriptions for parameters, so the description compensates by clearly explaining offset as 'Pagination offset' and limit as 'Maximum number of results,' including defaults and example calls. This adds concrete meaning beyond the bare schema properties.

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 'List users from AgencyAnalytics' and elaborates with 'Retrieves all platform users with their details and roles.' It uses a specific verb (list/retrieves) and resource (users), and differentiates from sibling tools like get_user by indicating the scope (all users vs. presumably 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 provides clear context that this tool is for listing all users, with examples showing default and custom usage. However, it does not explicitly mention when not to use it or name alternative tools like get_user, so it lacks explicit exclusions/alternatives.

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