list_triggers

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

No annotations provided, but the description implies read-only behavior by listing triggers. It discloses output format and filter behavior. Could be more explicit about potential performance or scope, but adequate.

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?

Three sentences, no wasted words. Purpose stated first, then parameter details, then pointer to related tool.

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 no output schema, the description provides output format clue. It covers usage, parameters, and relationship to sibling. Fully sufficient for a list tool.

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?

With 0% schema coverage, the description adds full meaning: explains database as key from list_databases, filter as case-insensitive regex on the formatted string with a concrete example.

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 it lists all user-defined triggers with a specific format, and differentiates from sibling tool get_trigger_source by advising to pass trigger name there instead.

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?

Explicitly tells when to use this tool (list all triggers) and when not to (for source code, use get_trigger_source). Also explains filter usage with examples.

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