Delete Agency Cron Job

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

The description is consistent with the destructiveHint annotation, but adds no extra behavioral context beyond what the annotation already signals. It does not state whether the deletion is permanent, what happens to associated data, or any side effects.

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 a single, short sentence that is front-loaded and free of filler. However, it is somewhat redundant with the title and could have used the space to add differentiating context, so it does not fully earn its place.

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 delete operation with fully documented parameters and a destructive hint, the description is minimally sufficient. Yet it lacks important contextual distinction from the analogous 'hosting_cron_delete' tool, and does not clarify the agency-specific scope, making it incomplete for seamless tool selection.

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 input schema provides full descriptions for both parameters (uuid and website_uid), covering all necessary details. The description adds no additional parameter semantics, which is acceptable given the high schema coverage.

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 ('Delete') and resource ('a cron job'), making the core action evident. However, it does not distinguish this tool from the sibling tool 'hosting_cron_delete', as it omits the 'agency' qualifier present in the title and name.

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 provides no guidance on when to use this tool versus alternatives like 'hosting_cron_delete'. There is no mention of prerequisites, context, or scenarios where this specific agency cron deletion is appropriate.

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