tdarr_kill_worker

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

No annotations provided, so description must fully disclose behavior. 'Kill' implies a destructive action, but it does not explain effects (e.g., termination of tasks, data loss, reversibility). Lacks necessary context for a potentially disruptive operation.

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?

Very short and to the point. No unnecessary words. Could be slightly improved with a bit more context without losing conciseness.

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 simple kill action with no output schema, the description is minimal. Lacks context on impact, error conditions, or how to obtain node and worker IDs. Among many sibling tools, more context would aid selection.

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 covers both parameters with simple descriptions ('Node ID', 'Worker ID'). Description adds no extra meaning beyond schema. Baseline 3 due to 100% schema coverage, but no value added.

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 ('Kill'), the resource ('a worker'), and the scope ('on a node'). It distinguishes from sibling tools like tdarr_cancel_worker_item which cancels a worker item rather than killing the worker itself.

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 on when to use this tool versus alternatives like tdarr_cancel_worker_item or tdarr_disconnect_node. No mention of preconditions or exclusions.

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