b24_crm_timeline_add

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 states the add action but does not mention required permissions, whether the operation is reversible, what happens with a read-only webhook, or what the response looks like. This is a meaningful gap for a mutation tool.

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 concise sentence with no filler words, making it easy to scan. It loses a point because the 'o actividad' phrase is slightly misleading and the sentence does not front-load any distinguishing constraints or alternatives.

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 mutation tool with no annotations and no output schema, the description is too thin. It omits when to use it, the webhook/authentication requirement, what input combination is necessary to avoid read-only failure, and what a successful call returns. The schema covers parameter basics, but the tool-level description does not provide enough operational context.

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 80%, so the input schema already documents most parameters. The tool description adds no additional meaning about parameters; in fact, 'actividad' hints at a capability not represented in the schema. With high schema coverage, the baseline of 3 is appropriate.

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 ('Agrega') and a specific resource ('la línea de tiempo de un registro CRM'), so an agent can tell this is about adding something to a CRM record's timeline. However, it says 'comentario o actividad' while the input schema only supports a comment field, creating mild ambiguity, and it does not distinguish itself from siblings like b24_crm_update.

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?

There is no guidance about when to use this tool versus alternatives, no mention of prerequisites such as having write access via webhook, and no exclusions. The usage context is only vaguely implied by the description.

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