list_workflow_triggers

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

The readOnlyHint annotation already communicates the read-only nature, and the description is consistent with it. The description adds only the 'all triggers' scope and optional pagination, but does not disclose ordering, default page size, or response shape, which an agent might want to know for a tool without an output schema.

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 sentence with the core action front-loaded and the pagination qualifier placed immediately afterward. It contains no filler, no repetition of schema details, and every word earns its place.

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 read-only list tool with two optional, fully documented parameters, the description is largely complete. It does not specify return fields or default pagination behavior, but those details are not essential for an agent to select or invoke this tool correctly, especially given the read-only annotation.

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 100%, and both page and page_size already have descriptive schema entries. The description's mention of 'optional pagination' adds no meaning beyond the schema, so the baseline of 3 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?

The description uses a specific verb ('list') and resource ('workflow triggers'), clearly identifying a read-only enumeration operation. It is distinct from the singular get_workflow_trigger and from sibling tools like list_workflow_actions, though it does not explicitly contrast itself with those alternatives.

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 implies the tool should be used when all workflow triggers are needed, and mentions optional pagination. However, it provides no explicit guidance about when to choose this over get_workflow_trigger, list_workflow_actions, or list_workflows, and it does not state any exclusions or alternative conditions.

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