forget_torrent

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

With no annotations, the description carries full burden. It only reveals that files are kept, but omits what 'forget' entails (e.g., removal from list, tracker status) and fails to disclose side effects, permissions, or response behavior.

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 a single short sentence with no wasted words, which is appropriate, but it could be more informative without sacrificing conciseness (e.g., including parameter hint or usage note).

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?

Despite having an output schema and only one parameter, the description is too sparse. It fails to clarify how 'forget' differs from the sibling 'remove_torrent,' and does not leverage the output schema to describe return values, leaving the agent underinformed.

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%, and the description does not mention the 'torrent_id' parameter at all. The schema only provides a type, so the description adds zero semantic value for parameter usage.

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 the action 'Forget' on the resource 'torrent' and adds the key behavioral note 'keeping the files.' This makes the basic purpose unambiguous, but it does not differentiate from the sibling tool 'remove_torrent,' which may perform a similar action with file deletion.

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 guidance is provided on when to use this tool versus alternatives like 'remove_torrent.' The description lacks any usage context, prerequisites, or exclusions, forcing the agent to guess based on tool names alone.

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