list_torrents

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false). The description adds that filters are applied locally, but the phrase 'no filter value is sent as an arbitrary API endpoint' is vague and potentially confusing. No contradiction with annotations.

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 brief and the main verb/resource is front-loaded, which is good. However, the second clause is cryptic and does not earn its place, and the overall terseness borders on under-specification rather than deliberate conciseness.

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?

With five optional parameters, zero schema descriptions, and sibling tools that perform related listing/filtering tasks, the description is too sparse. It does not explain what the returned output contains, how filters interact, or when this tool is preferable to list_problem_torrents or analyze_largest_torrents.

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%, so the description must compensate for the five undocumented parameters, but it only says 'using local filters' without explaining limit, state, category, min_size_gib, or inactive_days. The parameter names are somewhat self-explanatory, but the description adds essentially no parameter-level meaning.

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 states the verb ('List') and resource ('torrents') clearly, and the phrase 'using local filters' signals that filtering is done client-side. However, the second clause about arbitrary API endpoints is confusing and does little to distinguish this tool from siblings like get_torrent_details or list_problem_torrents.

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 guidance is given for when to use this tool versus alternatives such as get_torrent_details, list_problem_torrents, or analyze_largest_torrents. The 'local filters' hint implies a listing use case, but there are no exclusions, prerequisites, or decision rules.

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