Delete website cron job

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds meaningful nuance by explicitly stating the operation is permanent and that deleting a nonexistent cron job succeeds without error. This goes beyond the bare hints and helps set correct expectations.

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 concise sentences with no unnecessary words. The primary action is front-loaded, and the idempotence clarification earns its place as a separate sentence.

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 two-parameter destructive operation with annotations covering idempotence and destructiveness, the description is nearly complete. It lacks explicit usage differentiation from similar delete tools, but otherwise gives an agent enough to invoke it correctly.

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%, so the schema already documents both parameters. The description adds some relational context ('identified by its uuid' and 'from an Agency Plan website') but does not materially deepen parameter understanding beyond what the schema provides.

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 specific verb ('deletes'), a specific resource ('cron job'), and scope ('from an Agency Plan website'). This clearly distinguishes it from account-level cron job tools like hosting_deleteAccountCronJobV1 and from the create/list cron job siblings in the same namespace.

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 it should be used when deleting a cron job from an Agency Plan website, but it does not explicitly state when to use it over alternatives or mention prerequisites such as listing cron jobs first. The idempotence note provides useful context but not routing guidance.

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