b24_crm_list

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

Without annotations, the description discloses key behaviors: supports filters, field selection, and automatic pagination. It is clear it is a read operation, though it does not explicitly state read-only or discuss rate limits.

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 concise sentences in Spanish, front-loading the primary purpose and key capabilities with no redundant information.

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?

Given the tool complexity (7 params, nested objects) and high schema coverage, the description covers core functionality (entity types, filtering, selection, pagination) but omits ordering and webhook_url, which are in schema.

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 coverage is 86%, and the description merely summarizes entity types and features without adding meaning beyond the schema's descriptions (e.g., for filter, select, all_pages).

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 lists CRM records, enumerating specific entity types (deals, contacts, companies, leads, quotes, SPA items), which distinguishes it from sibling tools like b24_crm_get (single record) or b24_crm_create.

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 listing use cases by listing entities, but does not explicitly contrast with alternatives (e.g., b24_crm_get for single records) or provide when-not-to-use guidance.

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