node_plugins_torrent_reports

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavioral context — that filters use expensive LIKE operators and can degrade database performance — which is real value beyond the structured fields.

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?

Two sentences, both earning their place: the first is the purpose, the second a performance caveat. Front-loaded and free of filler, though slightly more structure could separate the warning from the purpose.

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?

A no-arg-required read tool with no output schema and partially documented nested parameters. The description covers purpose and a performance caveat, but leaves sorting/filterModes semantics and return shape unexplained, which for a nested-object report tool is a meaningful gap.

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 only 33% (size and start documented; filters, sorting, filterModes, and globalFilterMode undocumented). The description only generically warns that 'filters' are expensive, adding no syntax, shape, or semantics for the four undocumented parameters, so it fails to compensate for the coverage gap.

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?

States a specific verb and resource ('Get Torrent Blocker Reports'), so the agent knows exactly what is retrieved. It does not distinguish itself from the nearby siblings node_plugins_torrent_stats or node_plugins_torrent_truncate, which an agent could easily confuse it with.

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 note that filters are 'primarily intended for use by the frontend' implies programmatic callers should be cautious, but there is no explicit when-to-use, when-not-to-use, or alternative tool named. Usage is only implied rather than directed.

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