Delete Workspace Job

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

Annotations already indicate destructiveHint=true, and the description adds valuable context by explaining what jobs do ('define which nodes run together') and the specific consequence of deleting the wrong one ('breaks scheduled pipelines'). No contradiction with annotations.

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 concise and front-loaded with the essential action and warning. It uses a single impactful sentence followed by a structured list of parameters and return value, with no redundant 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?

The tool has an output schema (unshown) and the description mentions 'Confirmation message' as return. Given the destructive nature, the description adequately covers behavior, safety, and consequences. Slightly more detail on the confirmation format could be added but is not necessary.

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 has 100% description coverage for all three parameters. The description's 'Args' list restates the schema's descriptions without adding new information, so baseline score of 3 is appropriate.

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 'Delete a job from a workspace' with a specific verb and resource. It distinguishes from sibling tools like 'create_workspace_job' and 'update_workspace_job' by warning about destructive consequences, making the tool's purpose unambiguous.

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 explicitly warns about the destructive nature ('deleting the wrong one breaks scheduled pipelines') and includes a safety confirmation parameter. While it doesn't name alternative tools, the warning provides clear context on when not to use it.

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