b24_crm_list

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

With no annotations, the description carries the transparency burden. 'Lista' clearly signals a read-only operation, and it discloses key behaviors: filtering, field selection, and automatic pagination. It does not discuss rate limits or response format in detail, but that is less critical for a non-mutating 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 two short sentences, front-loading the core purpose and resource, then listing supporting capabilities. Every clause adds useful information with no 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 9-parameter tool without annotations or an output schema, the description provides the essential invocation context: which entities can be listed and what operations are supported. The rich parameter schema fills in the remaining details, though the output shape is not mentioned.

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 high (89%), with per-parameter explanations and examples, so the baseline is 3. The description only broadly names filters, field selection, and pagination; it adds no syntax-level meaning beyond what the schema already provides.

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 states a specific action ('Lista') and resource ('registros CRM'), and enumerates the supported entity types: deals, contacts, companies, leads, quotes, and SPA items. This clearly distinguishes it from non-CRM list siblings and from b24_crm_get, which implies a single-record retrieval.

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 implies when to use the tool by mentioning filters, field selection, and automatic pagination for CRM records. However, it gives no explicit guidance about when not to use it or when to prefer related siblings such as b24_crm_get for single records.

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