Listar locuciones

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

Annotations already indicate readOnlyHint=true (safe read). The description adds valuable information: audio base64 is omitted by default to avoid saturation, and how to include it. This is a meaningful behavioral trait beyond the annotation.

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: first defines purpose, second explains a key parameter behavior. No redundant words; every sentence adds value. Efficient and 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?

Despite the tool's simplicity (one optional param, no output schema), the description fails to mention output fields (e.g., IDs, names) which are likely needed for subsequent operations like pbx_get_announcement. The openWorldHint suggests variability, but the description should still outline typical response content.

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% (no descriptions in schema). The description briefly explains the includeAudio parameter ('pásalo con includeAudio=true'), but lacks detail about its exact effect (include base64-encoded audio). With low coverage, the description should compensate more fully.

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 lists recordings/announcements (Locuciones/anuncios) with specific verb and resource, and the title 'Listar locuciones' reinforces that. It implicitly distinguishes from pbx_get_announcement (singular) by being a list operation.

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 provides context (listing announcements) and a condition (includeAudio parameter), but does not explicitly state when not to use this tool or mention alternatives like pbx_get_announcement for individual retrieval. Usage is implied but not fully guided.

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