ghl_delete_trigger_link

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

There are no annotations provided, so the description carries the full burden of behavioral disclosure. The description merely restates the tool's name, offering no additional context about irreversibility, permissions, side effects, or return behavior. It adds no value beyond what the name already implies.

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 a single concise sentence with no unnecessary words. It is front-loaded and easy to parse. However, it is under-specified, which limits its overall value, though that is more a matter of content than conciseness.

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 the tool's simplicity (one parameter, no output schema), the description is minimal but still incomplete. It does not explain what a trigger link is, how to find the linkId, or the consequences of deletion (e.g., whether it is a hard delete). More context is needed for an agent to confidently use this tool without additional assumptions.

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 schema has one parameter (linkId) with 0% description coverage. The description does not mention or explain linkId, leaving the agent to infer its meaning from the parameter name alone. Since schema coverage is low, the description was expected to compensate, but it fails to do so.

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') and the resource ('trigger link'), which distinguishes it from sibling tools like get_trigger_links and create_trigger_link. The verb+resource combination is specific and unambiguous.

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 provides no guidance on when to use this tool, any prerequisites, or alternatives. It simply states the operation without explaining the context (e.g., when a trigger link should be deleted) or any conditions under which it should not be used.

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