find_largest_torrent

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

No annotations are present, so the description must carry the burden of behavioral disclosure. It reveals the search/find nature and the size-based heuristic, but does not explicitly state that the operation is read-only, what happens with no matches, or whether it queries the indexer directly. The basic behavior is clear but not deeply transparent.

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?

A single front-loaded sentence with no redundant words. The verb and target come first, and the parenthetical adds the key heuristic without bloating the description.

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?

The tool is simple and has an output schema, so return values are covered. However, the description omits usage guidance and any mention of related tools or prerequisites (e.g., where indexer_id comes from), leaving the agent with an adequate but incomplete picture.

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?

The schema has zero description coverage, and the description only restates the two parameter names in prose ('IMDb id' and 'one indexer') without providing formats, acceptable values, or how to obtain an indexer_id. For a low-coverage schema, the description does not meaningfully compensate beyond the property names.

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 specifies a concrete action (find), a precise target (largest-sized search result), and scoping (for an IMDb id on one indexer). The parenthetical clarifies the selection heuristic, making it easy to distinguish from generic siblings like search_torrents or find_imdb_candidates.

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?

No explicit when-to-use or alternatives are provided; the description only implies the tool is for selecting the single largest result on one indexer. It does not mention when not to use it or contrast it with search_torrents, so guidance is only implicit.

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