get_c411_torrent_info

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

With no annotations provided, the description carries full disclosure burden but only states it's a read operation ('Get') targeting metadata. It fails to disclose what 'detailed metadata' specifically includes, error conditions for invalid hashes, rate limits, or caching behavior.

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?

Single sentence of 10 words with zero waste. Front-loaded with action verb 'Get', immediately identifies the resource (c411.org torrent metadata), and specifies the lookup key (infoHash). Every word 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?

Appropriate for a simple 1-parameter tool with output schema present (no need to describe return values). Sufficient for invocation but could be improved by explicitly mentioning the sibling workflow (obtain hash via search_c411 first).

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 is 100% with the infoHash parameter fully documented including pattern validation. The description mentions 'by its infoHash' but adds no semantic meaning beyond the schema's existing '40-character hex infoHash' description, meeting the baseline for high-coverage schemas.

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 uses specific verb 'Get' with clear resource 'detailed metadata for a c411.org torrent' and scope identifier 'by its infoHash'. This clearly distinguishes from sibling download_c411_torrent (content vs metadata), get_c411_torrent_comments (metadata vs comments), and search_c411 (specific hash lookup vs broad search).

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 phrase 'by its infoHash' implicitly signals you must already possess the hash to use this tool, distinguishing it from search_c411. However, it lacks explicit guidance on the prerequisite workflow (search first, then this tool) or when to prefer alternatives.

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