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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly details ranking criteria (quality, efficiency, health, size, language), response requirements (top 3-5 results with specific fields), and fallback behavior for poor results (suggest keywords). This tells the agent exactly how the tool behaves and what to do with outputs, making the behavior highly 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?

The description is well-structured with a clear opening sentence followed by organized ranking and response sections. It is longer than a minimal description, but every section contributes actionable guidance for the agent. The use of headings and bullets improves scanability, though the ranking rules could be tightened without losing meaning.

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 description covers the full workflow: performing the search, analyzing and ranking results, formatting recommendations, and providing fallback keyword suggestions. Even if the output schema exists, the description specifies exactly what the agent should deliver, which is more than enough for correct invocation and use. Nothing critical is missing for an agent to handle this tool effectively.

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 input schema already provides 100% coverage, with a detailed description for 'query' that includes optimization rules and a clear explanation for 'user_intent'. Since schema coverage is high, the description does not need to add parameter semantics. The main description adds no further parameter-level meaning, so the baseline of 3 is appropriate.

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 opens with 'Perform an advanced torrent search across multiple providers,' which clearly identifies the tool's function as a search across torrent providers. It differentiates from siblings like popular_torrents and get_torrent by the nature of the operation, but it does not explicitly name or contrast alternatives. The core purpose is clear, though sibling differentiation is implicit.

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 description provides extensive guidance on how to rank and present results, but it does not state when to use this tool versus alternatives like popular_torrents or available_sources. The usage is implied by the search-oriented name and description, yet there is no explicit exclusions or 'use this when' context. It offers strong procedural guidance inside the tool but not tool-selection guidance.

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