whatsms_admin_get_users

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

With no annotations, the description carries the full burden of behavioral disclosure. It notes 'optional pagination', which suggests large result handling, but omits details like authentication requirements, sorting, defaults, or whether the operation is strictly read-only (though 'List' strongly implies so). It is not misleading but lacks depth.

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, clear sentence that is immediately understandable and front-loaded. Every word adds value with no redundancy or filler.

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 simple list tool with no output schema and no annotations, the description adequately communicates the core purpose and hints at a pagination feature. It could mention expected return fields or authentication context, but given the low complexity, it is largely complete.

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 input schema is empty with zero parameters, so the baseline is 4. The description adds 'optional pagination' but does not define parameter names or formats, which is acceptable given no parameters are formally declared, but leaves practical invocation details unspecified.

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 the specific verb 'List' with the resource 'users in the WhatSMS system', clearly distinguishing it from sibling write tools like whatsms_admin_create_user and whatsms_admin_update_user. Mention of 'all users' and 'optional pagination' further clarifies scope.

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?

Usage context is implied rather than explicit: it is the 'get/list' counterpart to user management CRUD operations. No exclusions or alternative tools are mentioned, and there is no guidance on when to use pagination versus not.

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