Delete trigger link

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

The description says 'Destructive,' which only repeats the destructiveHint=true annotation already present. It does not add behavioral detail beyond the annotations, such as whether deletion is permanent, cascades to related data, or requires special permissions.

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 extremely short and front-loaded with the core action. The 'Destructive' sentence is redundant with the annotation, so it does not fully earn its place, but the overall structure is compact and easy to parse.

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 simple one-parameter destructive operation with annotations covering the safety profile, the description is minimally viable. However, it lacks context about the permanent effect, whether the trigger link must exist, or what the response looks like.

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 0%, and the description does not explain linkId beyond what the schema already shows. The parameter name is somewhat self-explanatory, but the description adds no meaning about how to obtain or format the link 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 a specific action ('Delete') and resource ('trigger link'). The tool name and sibling tools make its role distinct from ghl_create_trigger_link and ghl_list_trigger_links, so an agent can easily understand what this tool does.

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 intended usage is implied by the delete verb and the required linkId parameter, but there is no explicit guidance about when to choose this tool over alternatives, prerequisites, or exclusions. No when-not-to-use context is provided.

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