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

Annotations already cover readOnly, idempotent, openWorld and non-destructive semantics, so the safety profile is handled. The description adds one genuinely useful behavioral note — that the upstream endpoint is experimental and may be unstable — but says nothing about auth approval (approval_id) or the governance/routing parameters.

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 short sentences, action first, caveat second — nothing wasteful. It is only 'concise' because it is thin, but structurally it is well front-loaded.

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 definition should explain the return shape (list of advice objects with severity/detail) and the governance parameters. Neither is present, so an agent can invoke it but not predict or interpret the result.

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 burden and contributes nothing: no explanation of project_ref's format, the approval_id requirement for what looks like a gated call, or the beon_* context/route parameters. An agent cannot infer the meaning of most inputs from either source.

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 a verb and resource ("Inspect security advisors"), which distinguishes it from most siblings but not from its natural counterpart supabase_get_performance_advisors. It never says what a security advisor actually is (e.g., DB lint findings such as RLS-disabled tables), so an agent must guess the domain.

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 when-to-use guidance, no prerequisites, and no mention of the sibling supabase_get_performance_advisors as the alternative for performance checks. Usage is only implied by the word "inspect".

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