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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds one genuine trait beyond that — the call works 'without credentials' — but says nothing about auth scoping, what subset of metadata is exposed, or any rate limits.

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?

A single five-word sentence with no filler and the key constraint front-loaded. It is efficient, though the extreme brevity is better characterized as under-specification than as disciplined conciseness.

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?

For an 8-parameter tool with no output schema and zero schema descriptions, the description is far too thin: it does not say which parameters matter, what metadata comes back, or how project_ref should be formed. Only the credential-free behavior is conveyed.

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 description coverage is 0% across 8 parameters, so the description carries the full explanatory burden and supplies none. The required project_ref is never explained (its 20-lowercase-character pattern is not hinted at), and the beon_* plumbing parameters are entirely unaddressed.

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 verb 'inspect' plus 'project metadata' names a resource, but 'metadata' is broad and does not separate this from siblings like supabase_list_projects, supabase_get_database_config, or supabase_get_auth_config. An agent can guess the general area but not the exact scope of what is returned.

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?

There is no when-to-use guidance and no named alternative. The only contextual signal is the 'without credentials' phrase, which implies this is the low-friction read path, but the description never says when to prefer it over supabase_list_projects or the config-specific getters.

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