supabase_list_users

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

With no annotations, description carries burden of explaining return structure (email, phone, metadata, confirmation status) and pagination behavior. However, lacks details on rate limits, authentication requirements, or error conditions.

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?

Two efficient sentences. Front-loaded with purpose, followed by return value details. '[UNIFIED]' prefix is noise but doesn't obstruct readability.

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?

Covers core purpose and return values adequately for a list operation, but incomplete given 0% schema coverage—required 'site' parameter and pagination controls need explicit documentation in description.

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 has 0% description coverage. While description mentions 'pagination' conceptually hinting at page/per_page, it completely fails to document the required 'site' parameter or explain parameter syntax/defaults.

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?

States specific verb (List) and resource (users) and mentions pagination scope. Implies 'all users' distinction from siblings like supabase_get_user, though lacks explicit differentiation from supabase_search_users.

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?

Provides no guidance on when to use this versus supabase_get_user (single user lookup) or supabase_search_users (filtered queries). Does not mention that 'site' parameter is required for multi-tenant contexts.

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