deployado_delete_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 carried by structured data. The description adds no context beyond that — no statement about irreversibility, cascading effects on run history, required permissions, or error conditions — so it contributes essentially nothing to behavioral understanding.

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 single sentence is front-loaded and free of padding, but its brevity reflects under-specification rather than efficiency — there is no waste because there is almost no content.

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 destructive mutation with no output schema, the description should explain effects and irreversibility. With annotations covering only the safety hint, an agent still cannot tell what deletion actually does (removes schedule only vs. history) or what it returns.

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?

Both required parameters (app_id, cron_id) are fully documented in the schema at 100% coverage, so the schema carries parameter meaning. The description mentions neither parameter and adds no usage nuance such as whether cron_id is app-scoped.

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 is essentially the tool name and annotation title restated ('Delete a cron job'). It conveys the verb and resource but adds no distinguishing detail versus siblings such as deployado_list_cron_jobs or deployado_update_cron_job, so an agent learns nothing beyond what the identifier already says.

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?

There is no guidance on when to use this over alternatives, no prerequisites (e.g., whether the job must be stopped first), and no warning about the destructive nature beyond what the annotation covers. Usage is only inferable from the tool name.

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