Descargar audio de buzón a disco

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

Annotations declare readOnlyHint=true, but the description indicates the tool saves audio to disk, a clear write operation. This is an annotation contradiction. Additionally, no other behavioral traits (like file overwrite rules or size limits) are disclosed. The openWorldHint does not resolve the inconsistency.

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 two sentences and no filler. However, it could include more detail without becoming verbose. For a simple tool, this is acceptable but not perfect.

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 3 parameters, no output schema, and contradictory annotations, the description lacks critical details: exact output format, error cases, auth requirements, and disk location. Sibling tools suggest a recordings ecosystem, but the description does not leverage that 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?

With 0% schema description coverage, the description must explain parameters. It does not mention extensionId, voicemailId, or filename. Only the purpose of the tool implies voicemailId identifies the message, but no explicit semantics are added. The filename parameter's role is unclear.

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 tool downloads voicemail audio and saves it to a folder, returning the local path. It distinguishes from siblings like pbx_get_recording_url (which returns a URL) and pbx_get_voicemail (which gets metadata). The verb 'descarga' and resource 'audio de buzón' are specific.

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 is provided on when to use this tool versus alternatives like pbx_get_recording_url or pbx_download_recording. No prerequisites or when-not-to-use conditions are mentioned. The description assumes the agent already knows the context.

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