Delete Sub Job

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

Beyond annotations, the description provides additional behavioral context: permanent deletion, irreversibility, API endpoint details, and a deprecation note. This adds value beyond the destructiveHint annotation.

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 structured but contains redundancy (e.g., 'This cannot be undone' appears twice). It could be more concise while still conveying key information.

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 delete operation with annotations providing safety signals, the description covers purpose, irreversibility, required parameters, and API context. It is sufficiently complete given the tool's simplicity.

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 already fully describes both parameters (id, project_id) with clear descriptions. The description merely repeats that they are required, adding no new semantic meaning.

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 specified Sub Job' and elaborates that it permanently removes Work Breakdown Structure records. This distinguishes it from sibling tools that delete other resources (e.g., delete_submittal, delete_budget_line_item).

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 mentions a deprecation note and a replacement endpoint but does not explicitly state when to use this tool versus alternatives. It implies usage for permanent deletion but lacks clear when-to-use or when-not-to-use guidance.

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