list_trigger_links

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

The readOnlyHint annotation already tells the agent this is a safe read, so the behavioral bar is lower. The description adds the useful scope constraint of 'current GoHighLevel location' and hints at the return content ('link names and IDs'), which is modest value beyond the annotation but not rich behavioral context.

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 short sentences, front-loaded with the action and scope, and the parenthetical clarification earns its place. No filler.

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 zero-param read tool with a readOnlyHint annotation and no output schema, the description is adequate. However, it offers no guidance on pagination, filtering, or when the location context matters, which an agent might need for a list 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?

The tool takes zero parameters, so there is nothing for the description to explain beyond scope. Baseline 4 applies. It does clarify 'current location' as the implicit scope, which is a minor gain.

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 gives a specific verb and resource ('List all trigger links'), clarifies the concept with a parenthetical ('one-click action links'), and names the scope ('current GoHighLevel location'). It does not explicitly differentiate from siblings like list_tags, but the resource is specific enough that confusion is unlikely.

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?

No when-to-use guidance, no prerequisites, and no alternatives named. The description implies a read operation but says nothing about when an agent should reach for this tool versus any other list_* sibling.

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