get_podcasts_by_id_clear_queue

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

The description directly contradicts the annotations. 'Clear episode download queue' implies a state-changing operation, yet annotations declare readOnlyHint: true and destructiveHint: false. This would mislead an agent into believing the operation has no side effects, which is unsafe for a clear action.

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 concise and front-loaded with the core purpose, followed by the endpoint and args. It avoids unnecessary wordsholence, but the brevity means some useful behavioral detail is missing.

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?

Although the tool is simple and an output schema exists, the description fails to explain side effects or reconcile the contradiction with annotations. It also lacks usage guidanceches. The agent cannot safely invoke this tool correctly given the conflicting signals.

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 0%, so the description must compensate, but it only says 'id: Path parameter.' This adds no semantic meaning beyond the schema's type string and required flag. It does not explicitly state that id is the podcast ID or clarify its format or scope.

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 explicitly states the action and target: 'Clear episode download queue.' This is a specific verb + resource, and the HTTP path clarifies the exact endpoint. It is clearly distinct from sibling tools like get_podcasts_by_id_downloads or get_podcasts_by_id_checknew.

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 no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The only implied context is that it clears a queue, but there is no explicit routing or comparison to siblings.

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