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 only says 'Retrieve a list of users' without mentioning any behavior such as pagination, default sorting, archived filtering, auth requirements, or that it is a read-only operation. This leaves significant gaps for a 9-parameter tool.

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, efficient sentence that immediately conveys the core function. It wastes no words, but it may be under-specified for the tool's complexity. This is concise and front-loaded, though it sacrifices helpful detail.

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 tool with 9 parameters, no annotations, and no output schema, the description is far from complete. It fails to explain pagination behavior, parameter semantics, or any typical usage context. The minimal information leaves the agent guessing about how to structure calls and interpret results.

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 11%, and the description adds no parameter information. While parameter names like 'page' and 'email' are somewhat self-explanatory, ambiguous ones like 'portal_member_company_id' remain unexplained. With low coverage and no description compensation, this dimension has clear deficiencies.

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 retrieves a list of users, using a specific verb 'Retrieve' and resource 'users'. It distinguishes itself from singular 'get_user' by indicating plural 'list', though it lacks explicit scope clarification. This is clear enough but not as detailed as the high-caliber example.

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?

There is no guidance on when to use this tool versus alternatives like get_user or other list_* tools. The description gives no context about typical use cases, filtering scenarios, or relationships with sibling tools, so the agent has no help choosing among similar tools.

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