add cron job

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds that it executes a verified command v-add-cron-job and mentions 'arbitrary shell command', which hints at flexibility and potential risk, but does not elaborate on side effects, permission requirements, or failure modes. It adds some context without contradicting annotations.

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 two short sentences with no wasted words. The primary purpose is front-loaded, and the second sentence adds a relevant implementation detail. It is efficiently 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?

Given the tool's complexity (10 parameters, 8 required, low schema coverage, and an output schema), the description is far too sparse. It does not explain the schedule fields, the confirm requirement, the restart option, or the meaning of jobId. The agent is left without essential guidance on how to construct a valid call, making the description incomplete for a tool of this complexity.

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 only 10% (only the confirm parameter has a description), so the description must compensate for the lack of parameter documentation. However, the description only hints at the command parameter via 'arbitrary shell command' and gives no information about schedule fields (minute, hour, day, month, weekday), user, restart, or jobId. This leaves most parameters poorly explained.

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 'Create' with resource 'cron job' and specifies it executes an arbitrary shell command. This distinguishes it from siblings like list_cron_jobs and delete_cron_job, making the tool's purpose unambiguous.

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 used for creating cron jobs but provides no explicit guidance on when to use it versus alternatives (e.g., listing or deleting cron jobs). There is no mention of prerequisites or exclusions, leaving the agent to infer usage from the name and purpose.

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