cadlens_delete_job

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

With no annotations, the description carries the full burden. It discloses that the operation is irreversible and that it also removes the uploaded file and preview image, which is beyond the obvious 'delete job' action. It does not mention error behavior or idempotency, but the destructive scope is clear.

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 concise sentence that front-loads the primary action and immediately states consequences. Every word adds value, with no waste.

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 tool with one parameter, the description covers key behavioral aspects like irreversibility and associated file deletion. However, it lacks usage context, parameter semantics, and any mention of return behavior or error conditions, leaving gaps given absent annotations.

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 schema contains only job_id with no parameter description, and schema coverage is 0%. The tool description does not mention job_id or explain its meaning, format, or how to obtain it, failing to compensate for the schema gap.

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 clearly states the tool deletes a job and its associated files/preview image, with a specific verb and resource. It distinguishes itself from sibling tools like get_job and parse_file by indicating a destructive removal action.

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?

No guidance is provided on when to use this tool versus alternatives, such as whether deletion should occur after job completion or if there are prerequisites. The description offers no exclusions or cautions beyond irreversibility.

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