Delete Company Segment Item

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

The description repeatedly states the action cannot be undone, aligning with annotations' destructiveHint=true. It adds emphasis on permanence beyond annotations. No contradiction found.

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 short but contains repetition ('Permanently removes the specified Work Breakdown Structure records' appears twice). The key information is front-loaded, but conciseness suffers slightly.

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 three required parameters and no output schema, the description provides sufficient context: purpose, permanence, required params, and API endpoint. Annotations fill gaps like idempotency.

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% with clear descriptions for each parameter. The description merely lists the required parameters without adding extra meaning, meeting baseline expectation.

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 action 'Delete a specific Company Segment Item' and identifies the resource as Work Breakdown Structure records. It distinguishes from the sibling 'bulk_delete_company_segment_items' by focusing on a single 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 implies usage for deleting a single segment item and notes permanence, but does not explicitly contrast with bulk delete or provide scenarios for when to choose this tool over others. Context is clear but excludes alternative guidance.

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