Delete WBS Segment

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

The description adds context beyond annotations by repeating that deletion is permanent and cannot be undone. It does not contradict annotations, and it provides additional emphasis on irretrievability.

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 contains redundant phrasing ('Permanently removes...' followed by 'This action cannot be undone'). It could be more concise by eliminating repetition while retaining 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?

No output schema is provided, and the description does not explain the response format (e.g., success/failure indicators, HTTP status codes). For a destructive tool, this omission reduces completeness.

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 description coverage is 100%, so the schema already documents parameters. The description mentions required parameters (company_id, id) but adds no new meaning beyond what the schema provides.

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 ('Delete') and resource ('WBS Segment'), stating it permanently deletes Work Breakdown Structure records. It clearly distinguishes from sibling tools by specifying the exact resource and endpoint, and names required parameters.

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 clearly indicates when to use the tool (to delete WBS records) and emphasizes permanence. While it doesn't explicitly mention when not to use or alternative tools, the context is clear for this destructive operation.

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