disable_crons

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

With no annotations, the description carries the full burden. It discloses that the tool pauses scheduling (a non-destructive mutation), but does not mention reversibility, effect on currently running tasks, or error behavior for invalid IDs. It adds some value but lacks rich behavioral context.

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?

Single, front-loaded sentence with no wasted words. It clearly states the action, target, and qualifier.

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 one-parameter tool with no output schema and no annotations, the description adequately covers purpose and key behavior. It could mention reversibility or interactions with sibling tools, but given the tool's simplicity, this is nearly complete.

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 has 100% coverage with a description for the 'ids' parameter, so baseline is 3. The description reinforces that IDs target cron tasks and adds the context of disabling/pausing, but does not provide additional format or constraint details beyond the schema.

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 a specific verb ('Disable') with a clear resource ('cron tasks') and method ('by ids'), and clarifies the effect as 'pause scheduling,' which distinguishes it from sibling tools like delete_crons or stop_crons.

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 phrase 'pause scheduling' implies this is for temporarily disabling rather than deleting or stopping, but the description does not explicitly state when to use this tool versus alternatives like delete_crons or enable_crons, nor does it name alternatives or exclusions.

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