itglue_delete_related_item

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

With no annotations, the description correctly labels the tool as destructive and mandates a confirm token. However, it omits details about side effects, idempotency, or post-operation state (e.g., whether the link is permanently removed).

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?

Two concise sentences: one for purpose and one for behavioral caveat. Front-loaded with no redundancy or wasted words.

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?

Given no output schema or annotations, the description covers the essential behavioral trait (destructive + required confirm) and purpose. It lacks information on success/failure responses but is adequate for a simple delete operation.

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%, so baseline is 3. The description adds no extra parameter meaning beyond the schema; it only reiterates the confirm token requirement without elaborating on parentType or id.

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 'Remove a related-item link from a parent resource,' specifying the verb and resource. However, it does not differentiate from sibling delete tools like itglue_delete_configuration, though the 'related-item' context inherently distinguishes it.

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 notes the destructive nature and required confirm token, but provides no guidance on when to use this tool versus alternatives (e.g., itglue_create_related_item or itglue_list_related_items) or prerequisites like authorization.

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