Get Torrent

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

With no annotations, the description carries the full burden, and it delivers a genuinely non-obvious behavioral detail: the magnet is wrapped in an untrusted-data fence, and the fenced value itself is the link while notice/tag lines are not. That directly affects how an agent consumes the result. It stops short of disclosing auth needs, error behavior for missing ids, or rate limits.

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, front-loaded with the purpose, followed by the essential result-parsing rule. No filler and every sentence earns its place.

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?

For a one-parameter getter with an output schema present, the description covers purpose and the non-obvious fencing semantics of the return value. It omits what happens when the id does not resolve, which is a minor but real gap for a lookup 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 description coverage is 100% and the single parameter already documents that the id is 'returned by a previous search_torrents or popular_torrents call.' The description repeats only 'by id' and adds no format or validation detail, so the baseline 3 applies.

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 and resource: 'Get the magnet link for a specific torrent by id.' That is concrete and distinct from search_torrents and popular_torrents. It does not explicitly name a sibling to differentiate against, which keeps it below a 5.

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?

'by id' and the schema note that the id comes from a previous search_torrents or popular_torrents call imply the use case (you already have an id). There is no explicit when/when-not guidance or comparison against forward_torrent or torrent_webapp, so guidance is only implied.

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