Listar colas

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering safety and variability. The description adds no further behavioral context (e.g., return format, ordering). Baseline 3 due to annotation coverage, but no extra value.

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 extremely concise, using only 3 words. It is front-loaded with the subject, but could be more explicit ('list all configured call queues') without adding bulk. Still efficient.

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 no output schema and no parameters, the description is minimal. It does not clarify what the list contains (names, IDs, objects). Annotations provide safety context, but the return format is ambiguous, leaving the agent without full guidance.

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 parameters, schema coverage is 100% and no param info is needed. The description does not add meaning beyond the schema, but baseline is 4 for zero-parameter tools. No additional explanation is required.

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 'Colas de llamadas configuradas' is a noun phrase defining queues, not an action phrase stating what the tool does. It relies on the title 'Listar colas' to convey the list action, but the description itself lacks a verb, making it unclear that it retrieves a list.

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 vs. alternatives like pbx_get_queue or pbx_queue_state. The description does not differentiate from siblings or suggest appropriate contexts.

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