agency-hosting_deleteWebsiteCronJobV1

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

No annotations are provided, so the description must carry the behavioral burden. It does so by disclosing that the deletion is permanent and idempotent, including that deleting a non-existent cron job succeeds without error. It does not mention permissions or other side effects, but the primary destructive behavior is clearly documented.

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 sentences long: the first states the purpose and scope, and the second provides the idempotency behavior. Every sentence is useful and there is no filler.

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 delete operation with no output schema, the description is complete enough. It covers what is deleted, the scope, the permanent nature, and the behavior when the target does not exist.

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%, and the schema already documents both website_uid and uuid, including that the uuid is returned by the list cron jobs endpoint. The description adds little beyond saying the uuid identifies the cron job, so it stays at the high-coverage baseline.

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 uses a specific verb and resource: 'Permanently deletes the cron job identified by its uuid from an Agency Plan website.' This clearly identifies the operation and scope, and the 'Agency Plan website' qualifier helps distinguish it from the sibling account-level cron job tools.

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 gives clear context by limiting the tool to Agency Plan website cron jobs and identifies the uuid as the target identifier. It does not explicitly call out the alternative sibling tool or state when not to use it, which prevents a top score.

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