list_torrents

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

No annotations provided, so the description carries full burden. It discloses filtering, sorting rules, and limit, but omits details like whether the tool is read-only, pagination behavior beyond limit, or performance implications. The description is adequate but not rich in behavioral context.

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 exceptionally concise: two sentences, front-loaded with purpose, and every word adds value. No redundancy or verbosity.

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?

Given four parameters, no output schema, and no annotations, the description covers inputs adequately but leaves some gaps: the 'compact per-torrent info' is vague, and total match count is mentioned but not return structure. Overall sufficient for a list tool but not fully complete.

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 0%, but the description adds meaning for all parameters: label (exact match), status (enum values), sort_by (with sorting direction rules), and limit (max count). This compensates well for the lack of schema descriptions, though some parameter details (e.g., default values) are already in the schema.

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 clearly states 'List torrents with compact per-torrent info,' using a specific verb and resource. It distinguishes itself from sibling tools like get_torrent (single torrent) and add_torrent by focusing on listing with filters and sorting.

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 details filtering, sorting, and limiting behavior, but lacks explicit guidance on when to use this tool versus alternatives. Siblings like get_torrent exist for individual retrieval, but no mention of search-like tools (none present). The context is clear enough for most use cases.

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