tdarr_pause

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

No annotations are provided, so the description carries the full burden. It usefully discloses that this is a global setting affecting ALL Tdarr nodes, which is real behavioral context, but it omits auth/permission needs, reversibility, and the dry-run/apply workflow implications beyond what the schema already states.

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 front-loaded sentence with the action first and the scope and motivating example second; zero filler or redundancy.

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 an unannotated global mutation tool with four parameters and no output schema, the definition is minimal but the schema does cover the dry-run/apply mechanics. It still leaves permission requirements and the consequences of a global pause undisclosed.

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 75%, so most parameters are already documented; the undescribed 'paused' param is partially covered by the description's 'Pause or resume' framing, implying a boolean toggle. The description adds little else beyond the schema's own apply/planHash explanations.

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 clear verb+resource pair ('Pause or resume all Tdarr nodes') and scopes it as a global setting, which reads unambiguously and separates it from read-only siblings like tdarr_status. It does not explicitly name an alternative tool, but the purpose itself is specific enough for selection.

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?

Provides one concrete usage context ('while the server is busy streaming'), which implies when to reach for it. However, it offers no when-not guidance, no prerequisites, and no alternatives, leaving usage conditions mostly to inference.

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