cleanuparr_get_job

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

The readOnlyHint annotation already discloses this is a safe read operation. The description adds no further behavioral context (e.g., pagination, error cases, or side effects). It merely lists job_type values, which is parameter information rather than behavioral disclosure.

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 exactly two sentences: a direct purpose statement and a list of valid values. Every word carries meaning, with no 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 a simple getter with one parameter and an output schema, the description covers the essential elements: it states the action and lists the possible job_type values. It lacks explicit usage guidance, but is otherwise complete for this low-complexity tool.

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 schema for job_type is just 'string' with 0% schema description coverage and no enum. The description compensates by enumerating valid values: QueueCleaner, MalwareBlocker, DownloadCleaner, BlacklistSynchronizer, Seeker, and CustomFormatScoreSyncer. However, 'Values include' suggests non-exhaustiveness, leaving slight ambiguity about whether other values are allowed.

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 uses the specific verb 'Get' with the resource 'one job', clearly indicating a single-job retrieval operation. Listing possible job_type values (QueueCleaner, etc.) adds specificity, though it doesn't explicitly distinguish from sibling list_jobs or trigger_job beyond the singular 'one'.

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 provides no explicit guidance on when to use this tool versus alternatives like cleanuparr_list_jobs or cleanuparr_trigger_job. The usage is only implied: call it when you know a specific job_type and want that job's details. No exclusions or alternative mentions.

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