supabase_list_roles

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

No annotations are provided, so the description carries full burden. While 'List' implies read-only behavior and the description mentions what is returned, it fails to disclose critical behavioral traits such as privilege requirements, pagination behavior, or rate limiting for this database admin operation.

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 with a single sentence that efficiently communicates the tool's function. The '[UNIFIED]' prefix appears to be metadata noise but doesn't significantly detract from the overall structure.

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 lack of output schema and 0% parameter coverage, the description is insufficient. It omits essential context for the 'site' parameter and provides no hints about the return structure or format despite being a data-retrieval 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 description coverage for the required 'site' parameter, the description must compensate but fails entirely. It provides no explanation of what 'site' refers to (e.g., project ID, URL), its format, or how to obtain valid values.

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 specifies the verb 'List' and resource 'database roles', distinguishing it from sibling tools like supabase_list_users or supabase_list_tables. It also clarifies what data is returned ('attributes and permissions'). The '[UNIFIED]' prefix is cryptic but doesn't obscure the core purpose.

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 provides no guidance on when to use this tool versus alternatives (e.g., supabase_get_user for specific role details), nor does it mention prerequisites like admin privileges typically required for listing database roles.

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