Parar de grabar una llamada en curso

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

Annotations indicate this is not read-only (readOnlyHint=false) and not destructive (destructiveHint=false), but description does not add any behavioral traits such as permissions required, side effects, or what happens if the call is not recording. OpenWorldHint=true suggests unforeseen side effects, but no clarification is given.

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 sentence, which is concise, but it lacks necessary detail. It could be more informative without becoming verbose. It is front-loaded but too minimal.

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 simplicity (1 param, no output schema), the description still misses essential context: prerequisites (call must be in recording state), error cases, and return behavior. Compares poorly to siblings like pbx_start_recording.

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 0%, and the description does not explain the callId parameter beyond 'indicated active call'. No format, source, or validation information is provided. The description should compensate but fails to add value.

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 it stops recording of an active call. The verb 'detiene' (stops) and resource 'grabación de la llamada activa' (recording of the active call) are specific. It distinguishes from siblings like pbx_start_recording and pbx_hangup.

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?

No guidance on when to use vs alternatives like pbx_hangup or pbx_start_recording. No context about prerequisites (call must be recording). The description does not help the agent decide between this and other call-modifying tools.

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