supabase_get_user

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

No annotations provided, so description must carry full behavioral burden. 'Get' implies read-only but doesn't confirm safety, error handling (what if ID doesn't exist?), rate limits, or what 'detailed information' includes.

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?

Single sentence, appropriately brief. However, the '[UNIFIED]' prefix is technical metadata that doesn't help the agent and should be removed or explained.

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?

Without annotations, output schema, or schema parameter descriptions, the description leaves significant gaps. No mention of error cases, return structure, or the purpose of the 'site' parameter.

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, description must document both parameters. It implicitly maps 'ID' to user_id but completely fails to explain the 'site' parameter (is it a URL, site ID, or configuration key?).

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?

Clear verb ('Get') and resource ('user') with specific identifier ('by their ID'). Distinguishes from supabase_get_user_by_email implicitly by referencing ID, but fails to distinguish from supabase_list_users or supabase_search_users which also retrieve user information.

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?

No explicit guidance on when to use this versus sibling tools like supabase_list_users (for bulk retrieval) or supabase_get_user_by_email (when email is known instead of ID). No mention of prerequisites like authentication requirements.

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