b24_users_list

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

With no annotations, the description carries the burden of behavioral disclosure. 'Lista usuarios activos' signals a read-only listing operation and the field list indicates output content. However, it does not mention pagination behavior, the default ACTIVE filter being overridable, webhook requirements, or response structure.

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 with no filler. Every phrase contributes either to the operation (list), the scope (active users), or the output fields.

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 six parameters, no annotations, and no output schema, the one-line description is not complete enough. An agent cannot determine pagination semantics, the effect of all_pages, or the response format, and the description also does not warn that the 'active users' scope is just a default filter that can be overridden.

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 already documents limit, start, filter, and select (67% coverage), and the description adds some meaning by mapping output labels like 'cargo', 'departamento', and 'estado online' to the likely select fields. However, all_pages and webhook_url are not described in either the schema or the tool description, so the description only partially compensates.

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 ('Lista') and resource ('usuarios activos') and names the relevant output fields. It clearly identifies the tool as a user-listing operation, distinct from the CRM, tasks, disk, and calendar siblings.

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 clear context: use this tool to list active users with profile information. It does not explicitly name alternatives or say when not to use it, but there is no sibling tool with the same user-listing purpose, so the guidance is reasonably unambiguous.

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