List Automation Triggers

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description's simple 'List' statement is consistent and non-contradictory. It adds no extra behavioral details, but the annotations carry the burden adequately.

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?

A single, front-loaded sentence with 13 words. Every word is necessary and directly conveys the tool's function. No redundancy or fluff.

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 optional parameter, output schema present), the description covers the essential purpose. It could mention that the output is a list of trigger types, but the output schema likely handles that. No significant gaps.

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 input schema already describes the 'app' parameter as 'Filter triggers to a specific app slug' with 100% coverage. The description merely echoes this filter option without adding new meaning or format details, so baseline score applies.

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?

Description clearly states the action 'list' and the resource 'trigger types available in the automation catalog', with optional filtering by app. This distinctively specifies its function compared to sibling tools like list_automation_actions or list_automation_apps.

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 mentions optional filtering by app, which provides some usage context. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., list_automation_actions for actions). No when-not-to-use or exclusions are given.

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