list_users

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It does state that the limit has a maximum of 100, which is a useful constraint. However, it does not disclose whether the operation is read-only, whether pagination via offset is supported, or what the return structure looks like. The description is adequate but minimal for a list 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 a single, front-loaded sentence that immediately states the purpose and includes a key constraint. Every word earns its place, with no filler or repetition.

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?

With no output schema, no annotations, and 3 parameters, the description is far from complete. It fails to mention return format, pagination behavior (offset), or search semantics. An agent would struggle to know what to expect from the response or how to appropriately set the search parameter.

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 0%, so the description must compensate. It only explains the 'limit' parameter (max 100), leaving 'offset' and 'search' with no added meaning. The word 'search' in the description hints at the search parameter but does not clarify its behavior (e.g., partial vs exact match). This is insufficient for a 3-parameter tool.

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 'Search and list users' with a specific verb (search/list) and resource (users), distinguishing it from the sibling 'get_user' which implies a single user lookup. The mention of 'limit' further clarifies it's a list operation with a cap.

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 gives no explicit guidance on when to use this tool versus alternatives like 'get_user'. It does not mention exclusions or prerequisites. The only contextual hint is the limit constraint, but this does not help the agent decide between list_users and get_user.

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