cron_delete

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

Annotations declare destructiveHint=true, readOnlyHint=false, openWorldHint=false, so the agent knows this is a destructive, non-read-only local action. The description adds only the Russian phrase 'remove the cron task' plus a basic arg explanation. It does not detail permissions, irreversibility, or side-effects beyond what annotations already convey.

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 very short and front-loads the action. It includes arg information, though the formatting is terse and could be more structured.

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?

There is an output schema, so return values need not be described. However, for a destructive action with one parameter at 0% schema coverage, the description should provide more context on what 'task_id' represents and confirm the destructive consequence.

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 description coverage is 0%, so the description should compensate. It provides only 'task_id: ID задачи', which gives a minimal Russian label but no additional format or source details beyond the property name in 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 Russian phrase 'Убрать cron-задачу' states a specific verb and resource (remove a cron task). It clearly identifies the operation, though it doesn't explicitly differentiate itself from siblings like cron_edit or cron_toggle.

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 the tool is for deleting a cron job but offers no guidance on when to use it versus alternatives. With siblings such as cron_toggle and cron_edit, a user might need clarity on permanent deletion as opposed to toggling.

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