supabase_list_triggers

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

No annotations are provided, so the description carries the full burden. While 'List' implies a read-only operation, the description fails to disclose what data structure is returned, whether results are paginated, or any permission requirements needed to view triggers.

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 appropriately brief and front-loaded with the primary action. The '[UNIFIED]' tag is extraneous metadata that doesn't aid tool selection, but the remaining content is efficient with no redundant sentences.

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 absence of annotations and output schema, the description should provide more behavioral context. It adequately covers the basic listing function but leaves critical gaps regarding the 'site' parameter's expected format and the structure of returned trigger data.

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 description coverage, the description must compensate for both parameters. It explains the optional 'table' parameter via 'filter by table name,' but completely omits explanation of the required 'site' parameter, leaving significant semantic gaps.

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 the verb ('List') and resource ('database triggers'), distinguishing it from sibling tools like supabase_list_tables or supabase_list_policies. The '[UNIFIED]' prefix adds noise but the core purpose is unambiguous.

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 'Can filter by table name,' implying when to use the optional parameter. However, it lacks explicit guidance on when to use this over other schema inspection tools or prerequisites like requiring a specific site/project.

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