add_torrent

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

No annotations, but description discloses key behaviors: addition not verified, need to check list_torrents. Could mention if it's destructive or authorization needs, but still informative.

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 concise sentences with no waste. First sentence states purpose, second adds constraints, third gives warning. Well 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 all necessary aspects: input sources, parameter constraints, optional fields, start flag, verification caveat. No output schema needed. Complete for an add tool.

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 coverage 0%, so description compensates. Explains mutual exclusivity of magnet_or_url and file_path, optional label/directory, and start behavior. Lacks exact format hints but sufficient.

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?

Clearly states it adds a torrent from magnet link, URL, or local .torrent file. Distinguished from siblings by specifying the action 'add' and the input types.

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?

Tells to provide exactly one of magnet_or_url or file_path, optional label and directory, and start=False for stopped. Also advises verifying with list_torrents.

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