node_plugins_torrent_truncate

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

Annotations already flag readOnlyHint=false and destructiveHint=true, so the safety profile is disclosed structurally. The description adds nothing beyond that — it does not state that report data will be permanently lost, what the blast radius is across nodes/plugins, or whether the action is reversible.

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 four-word fragment with no filler, so it is compact and front-loaded. But at this length it is under-specified rather than genuinely concise, and it does not carry enough structure to orient the agent.

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?

For a destructive, parameterless operation with no output schema, the description should at minimum delineate what gets destroyed and over what scope (global? per plugin?). None of that is present, leaving the blast radius of a destructive call unexplained.

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 tool takes zero parameters, so there is no parameter meaning for the description to add or omit; the baseline for a parameterless tool applies. Scores above 4 would require the description to compensate for something the schema cannot express.

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?

Names a specific verb (truncate) and resource (Torrent Blocker Reports), so it is not a pure tautology of the tool name. However, it never clarifies what truncation actually means for the reports — purge everything, trim oldest entries, reset counters — leaving the scope of the operation ambiguous.

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 when-to-use guidance at all, and no mention of the closely related siblings node_plugins_torrent_reports and node_plugins_torrent_stats that an agent would plausibly confuse this with. The agent must infer the selection context entirely.

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