cleanuparr_trigger_job

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

The description adds the constraint that Seeker cannot be manually triggered, which is useful behavioral context beyond the destructiveHint annotation. However, it does not describe side effects, required prerequisites, or whether the action is reversible. The annotation already covers destructiveness, so this is acceptable but not rich.

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 two short sentences with the main action front-loaded. It conveys the core purpose and one key constraint without any fluff, making it highly concise and easy to parse.

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 destructive annotation, the description omits any guidance on the job_type parameter, which is critical for correct invocation. The tool appears simple (1 param) but the missing parameter semantics make it incomplete for an agent to use confidently.

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 0% — the single required parameter job_type has no description or enum. The description does not mention job_type at all, leaving the agent without any information on what values are valid or what the parameter means.

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's action: 'Run a one-time job now.' It is specific about the operation (manual trigger) and adds a scope constraint ('Seeker cannot be manually triggered'), which distinguishes it from other job-related tools. However, it does not explicitly differentiate from the similarly named cleanuparr_start_job, leaving some ambiguity.

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 gives no explicit guidance on when to use this tool versus others like cleanuparr_start_job or cleanuparr_update_job_schedule. It only notes that Seeker cannot be manually triggered, which is a restriction but not a usage directive.

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