seerr_schedule_job

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

The description says 'WRITE: this modifies your Seerr instance,' which merely restates the annotation readOnlyHint=false. It does not disclose additional behavioral traits such as what changes are made to the schedule, whether modifications are reversible, or any side effects beyond the generic 'modifies' statement.

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 one sentence, but it is under-specified. It offers minimal content and does not use the available space to convey useful information about the tool's behavior or parameters.

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 tool with 2 parameters (one nested object with additionalProperties) and an output schema, the description is entirely insufficient. It does not explain the request shape, what job_id refers to, or what the body should contain, making it nearly impossible to invoke the tool correctly.

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 description coverage is 0%, and the description does not explain the meaning or purpose of job_id or body. The schema shows these parameters but gives no semantic context, and the description fails to compensate, leaving agents uncertain about how to fill them.

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 states a clear verb and resource ('Modify job schedule'), which distinguishes it from sibling tools like seerr_run_job and seerr_cancel_job. However, it does not specify what kind of modification is possible (e.g., enabling/disabling, frequency), 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?

There is no guidance on when to use this tool versus alternatives. It does not mention related tools such as seerr_list_settings_jobs or seerr_run_job, nor does it provide context about prerequisites or typical use cases.

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