Click-to-call externo (dos números)

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

The description adds the warning '⚠️ Hace sonar teléfonos reales', indicating real phones will ring. This goes beyond the annotations (readOnlyHint false, destructiveHint false) to explain the real-world impact. It also implies the tool initiates calls, which is not fully captured by annotations.

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 extremely concise: two sentences that state the action and a key warning. No filler, and the most important information is front-loaded.

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 simple action like connecting two numbers via callback, the description is adequate but minimal. It lacks details about return values (no output schema), error conditions, or what happens after the call connects. Given the complexity (6 parameters), more context could be beneficial.

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 50% (3 of 6 parameters have descriptions). The tool description does not add additional meaning to parameters beyond what is in the schema. For example, it mentions 'from' and 'to' but not their roles in more detail. Baseline 3 is appropriate given moderate coverage.

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 verb 'conecta' (connects) and the resource (two numbers via PBX callback). It specifies 'cualesquiera from y to' indicating any numbers. However, it does not explicitly distinguish from sibling tools like pbx_originate_call or pbx_click_to_call_queue, which might have similar functionality.

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 on when to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or provide any context for selection. The description only states what it does, not when to choose it.

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