Listar buzones de voz de una extensión

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

Annotations already provide readOnlyHint=true and openWorldHint=true, so the description's mention of 'voicemails of an extension' adds minimal behavioral context beyond the safe read nature. No contradictions.

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?

Single, focused sentence with no wasted words. Front-loaded with the main action and resource.

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 tool's simplicity (1 param, readOnly, no output schema), the description adequately covers the core functionality. Missing output format details but acceptable for a list operation with sibling tools for details.

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%, but description adds 'por su id interno' clarifying that extensionId is the internal ID. However, no details on format or how to obtain it. Partially compensates for lack of schema description.

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 lists voicemail messages for an extension by its internal ID, using specific verb 'Listar' and resource 'buzones de voz' (voicemails). It distinguishes from siblings like pbx_get_voicemail (single) and pbx_delete_voicemail (delete).

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 when needing all voicemails for an extension, but does not explicitly state when to use versus alternatives like pbx_get_voicemail or pbx_mark_voicemail_read. No 'when not to use' or alternative naming.

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