workflow_management

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

With no annotations, the description carries the full burden for behavioral disclosure. It only reveals that workflows are long-running and 'tricky', but doesn't mention potential side effects, rate limits, dry_run behavior, or whether actions are asynchronous. This is insufficient for a tool with many mutation-like actions.

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 concise at two short paragraphs and front-loads the primary purpose. The 'PORTMANTEAU PATTERN RATIONALE' adds context but could be integrated more smoothly; still, no words are wasted.

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 the tool's complexity (14 parameters, 8 actions) and presence of an output schema, the description provides only high-level context about long-running workflows. It doesn't explain how actions interrelate or when to use dry_run/rate_limit, relying heavily on the schema for full understanding.

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 input schema provides 100% parameter descriptions, including action-specific requirements and defaults, so the description doesn't need to add parameter detail. The description adds no extra semantics beyond the schema's existing thorough documentation.

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 tool is for managing complex, multi-step torrent workflows, with a concrete example of downloading entire anime franchises. While it distinguishes itself from simple torrent operations, it doesn't enumerate the specific actions covered, making it somewhat broad.

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 implies this tool is for long-running, 'tricky' workflows that could take days, but it doesn't explicitly state when to use it over sibling tools like torrent_management or agentic_rtorrent_workflow. No alternatives or exclusions are mentioned.

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