stremio_streaming_server_purge_cache

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

With no annotations, the description carries the full behavioral burden and does disclose key traits: it stops matching torrent engines before deleting, requires confirm=true as a safety gate, and exposes the destructive scope (one torrent vs the complete desktop cache). It stops short of stating irreversibility or permission requirements.

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?

Three short sentences, front-loaded with the action, with zero filler. The mode-selection rule follows immediately, making it easy to scan.

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?

An output schema exists, so return values need not be described. For a destructive two-parameter tool with no annotations, the description covers the confirmation gate and the two purge scopes adequately, leaving only minor gaps such as reversibility.

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, and it does: confirm is explained as needing to be set true, and info_hash is defined as either a single torrent selector or empty for a full-cache purge. Both parameters gain meaning beyond the bare schema.

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?

States a specific verb (Delete) and resource (cached torrent data), plus the secondary action of stopping matching torrent engines. An agent can tell it is the destructive counterpart to the cache-listing sibling, though no sibling is named explicitly to sharpen the distinction.

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 tells the agent how to invoke it (set confirm=true; pass one info_hash or leave empty for a full purge), which is genuine usage guidance. However, it never states when to choose this over alternatives like stremio_streaming_server_cache, so context selection is only implied.

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