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

With no annotations, the description carries the full burden, and it does disclose one genuinely important trait: a run already started still finishes. It does not say whether no further runs are scheduled immediately, whether deletion is reversible, or whether permissions are required, leaving the mutation profile partly opaque.

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?

Two terse sentences with zero filler; the core action is front-loaded and the caveat follows immediately. Nothing could be removed without losing 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?

For a one-parameter deletion tool with no annotations and no output schema, the description covers the action and the key side effect on running jobs. The remaining gap is minor: recoverability and immediate scheduling effects are unstated, but an agent can call this correctly from what is given.

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 100% and the single required field already has a description with an example, so the schema does all the work. The description adds nothing about the identifier beyond what is structured, which is the expected baseline for one well-documented parameter.

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?

"Stop and remove a cron" names a specific verb pair and the exact resource, which cleanly distinguishes it from siblings like cancel_task and delete_secret. It stops short of explicitly contrasting itself with cancel_task, whose name could tempt an agent to cancel a running job instead of deleting the schedule.

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?

Usage is only implied by the verb: an agent can infer this is for permanent removal of a schedule. There is no explicit when-to-use/when-not-to-use guidance and no mention of cancel_task as the alternative for stopping an in-flight run, which is the most plausible confusion in this sibling set.

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