cron_toggle

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

Annotations already declare readOnlyHint=false, destructiveHint=false, so the mutation/non-destructive profile is covered. The description adds the concrete semantics of the toggle (1=disable/hide, 0=enable), which is genuinely useful. It does not state that the operation is reversible or whether it requires elevated permissions, so a 3 fits.

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?

Front-loaded action statement followed by a compact args block; no filler sentences. The docstring-style formatting is slightly verbose but every line carries information.

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?

An output schema exists, so return values need not be explained. For a two-parameter mutation, the description covers the action, the parameter origins, and value semantics. The only gap is the subtle conflation of 'disabled' with 'hidden', which could confuse an agent about side effects.

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%, so the description must carry the parameter burden, and it does: task_id is documented as coming from cron_list and is_hidden is given explicit value semantics (1=off/hide, 0=on). This meaningfully exceeds the bare 'integer' schema entries.

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 opening line gives a specific verb+resource pair: toggling the active state of a cron task. It clearly distinguishes the tool from cron_list, cron_add, cron_delete, and cron_edit by naming the distinct action (activity toggle). It stops short of a 5 because it does not contrast itself with cron_edit, which could plausibly also change task state.

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 implies when to use it (after obtaining a task_id from cron_list), which is a useful prerequisite hint. However, it gives no explicit when-not guidance or alternative — e.g. whether changing other fields should go through cron_edit instead.

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