queues_list

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

Annotations already provide readOnlyHint=true and destructiveHint=false. Description adds behavioral context about queues automatically scheduling posts with priority-based ordering, which goes beyond annotations and helps the agent understand the nature of queues. No contradictions with annotations.

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 concise sentences with no filler. Every sentence adds value: first sentence states purpose, second sentence provides useful context about queues. Front-loaded with the essential information.

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?

The description provides adequate context about what queues do, but does not describe the return format or any pagination behavior. Since there is no output schema, the agent lacks information about what fields the response will contain. While the tool is simple, some guidance on response structure would improve completeness.

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 description coverage is 100% for the single parameter, which has a clear description in the schema. The tool description does not add any additional meaning beyond what the schema already provides for the parameter. Hence baseline score of 3.

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?

Description clearly states 'List all posting queues' with specific verb and resource. Distinguishes from sibling tools like queues_create, queues_delete, queues_get, queues_update, and queues_next_slot by indicating it lists all queues.

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?

Description provides clear context that this tool lists all queues with an optional filter, but does not explicitly state when to use this tool versus alternatives (e.g., queues_get for a specific queue). No exclusion criteria or prerequisites mentioned.

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