get_queue_details

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

No annotations are present, so the description carries the burden of behavioral disclosure. It does reveal that the result is unpaged and includes per-episode detail, which is useful and non-obvious. However, it does not state that the operation is read-only, mention response-size caveats for an unpaged queue, or clarify behavior when no filters are supplied.

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 concise sentences with no filler. The primary behavior is front-loaded, and the practical use case is stated clearly in the second sentence. Every word adds value.

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?

There is no output schema, but the description covers the essential return content: full unpaged queue, per-episode detail, and the queue item id use case. The optional filter parameters are fully documented in the schema. A small gap remains in that the exact output shape beyond item ids is not described, but for this tool's purpose the description is adequate.

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?

All four parameters are fully described in the input schema, so the baseline is 3. The description adds no parameter-specific semantics beyond implying the include_* flags relate to per-episode detail, but it does not need to compensate because the schema coverage is complete.

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 states a specific verb and resource: it gets the full, unpaged queue with per-episode detail. The phrase 'unpaged' distinguishes it from the sibling get_queue, and 'useful for finding the queue item id of a specific episode' gives a concrete purpose.

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 a clear use case: when you need the queue item id for a specific episode, or want more detail than a paged queue would give. It does not explicitly name get_queue as the alternative or state when to avoid this tool, but the practical guidance is strong enough to route an agent.

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