Add a transfer to put.io

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

Beyond annotations (readOnlyHint=false, etc.), the description adds critical side effects: 'spends the account's bandwidth and storage' and requires user confirmation. This is valuable context not inferable from annotations alone.

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 sentences deliver the action, typical use, cost, and confirmation requirement without redundancy. Well-structured and front-loaded.

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?

Covers the core behavior, use case, and important cautions. With a 3-param schema and no output schema, the description is sufficient, though it doesn't mention progress tracking or cancellation alternatives.

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 descriptions already cover all parameters (100% coverage), including the meaning of url, confirm, and saveParentId. The description does not add new parameter-level details beyond what's in the 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?

The description clearly states 'Starts a download on put.io from a magnet link or HTTP URL' with a specific verb and resource. It also mentions typical sources (movies_find_torrents, shows_find_torrents), distinguishing it from sibling putio management tools.

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?

Provides context that this tool is typically used after torrent searches from movies_find_torrents or shows_find_torrents, and instructs to confirm with the user first. It does not explicitly list alternatives or when not to use it, but the use case is clear.

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