Descargar grabación a disco

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

Contradicts annotations: readOnlyHint=true implies no side effects, but description says it saves a file to disk, which is a mutation. openWorldHint is not leveraged to explain cross-system behavior.

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?

Two sentences, no fluff, each phrase adds value (downloads MP3, saves to specific dir, returns path).

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?

No output schema, but description mentions local path. Lacks details on overwrite behavior, directory existence, or permission checks. Adequate but not thorough.

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 100%, and description adds meaning: filename uses default <callId>.mp3, and the return path is for transcription. Adds value beyond schema.

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 downloads the MP3 of a call recording and saves it to a server directory, specifying the return value. This distinguishes it from siblings like pbx_get_recording_url, which likely returns a URL instead of saving to disk.

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 usage for server-side processing (e.g., transcription) by mentioning the local path is 'ready to transcribe'. However, it does not explicitly state when to use this over pbx_get_recording_url or exclude cases.

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