b24_crm_delete

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether deletion is permanent, whether confirmation or special permissions are needed, or that a write-capable webhook may be required. The only behavioral hint, 'read-only' without a personal webhook, lives in the schema rather than the description.

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 one short, front-loaded sentence with no wasted words. However, brevity comes at the expense of essential operational detail, so it is efficient rather than fully effective.

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 destructive tool with five parameters, no annotations, and no output schema, the description is under-specified. It omits webhook requirements, entity/scoping details, and any indication of expected behavior or errors, making it insufficient for reliable invocation in non-trivial contexts.

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 only 20%, and the description adds little beyond identifying that an ID is used. With five parameters, including entity, webhook_url, and entity_type_id, the agent gets no explanation of how they relate to the delete operation or whether entity_type_id or entity is needed alongside id.

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 verb ('Elimina' / deletes), a clear resource ('registro CRM'), and the key criterion ('por ID'). This cleanly distinguishes it from sibling tools like b24_crm_get, b24_crm_update, and b24_crm_list.

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 guidance on when to use this tool versus alternatives, no prerequisites such as write-enabled webhook configuration, and no exclusions or caveats. Usage context is only implied by the verb 'delete'.

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