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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the bar is lower. The description adds value beyond them by disclosing that authentication is required and by scoping what the result set contains (the three enumerated trigger types). No contradiction exists, and the remaining silence about return structure is minor for a read-only list tool.

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 19-word sentence with zero waste: verb+resource front-loaded, the scope-defining parenthetical immediately after, and the authentication requirement closing it. Every clause 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 low-complexity tool (one fully documented parameter, strong safety annotations, no nesting or enums), the description is nearly complete: purpose, scope, and auth are all covered. The only gap is that it never hints at the shape of returned trigger objects, which is a minor omission given no output schema exists.

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%: the only parameter, campaign_id, is fully documented with its type and provenance, so the schema does the heavy lifting. The description adds nothing parameter-specific, which matches the baseline-3 expectation for high-coverage schemas.

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 states a specific verb ('List') and a sharply defined resource ('automation triggers configured for an outreach campaign'), and the parenthetical enumerates what counts as a trigger (auto-reply rules, status updates, notifications), which adds real disambiguation value. This clearly separates it from siblings like list_campaign_replies (replies, not triggers) and list_outreach_campaigns (campaigns, not triggers) without needing to open any schemas.

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 use case is implied — you call this when you want the automation triggers for a specific campaign — and 'Requires authentication' hints at a precondition. However, the description gives no explicit when-to-use vs alternatives guidance, no exclusions, and no naming of sibling tools; the workflow hint (campaign_id comes from list_outreach_campaigns) lives in the schema, not the description.

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