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

Annotations fully cover the safety profile (readOnlyHint, idempotentHint, destructiveHint false, openWorldHint). The description adds only resource scope and the word 'Inspect'; it discloses no additional behavioral traits such as permissions, rate limits, or return behavior. With annotations carrying the safety burden, this is minimally acceptable.

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 four-word sentence is front-loaded and free of filler. However, it is too sparse to be appropriately sized for an 8-parameter tool, leaving no room for required context.

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 0% schema description coverage and no output schema, the description is not complete enough. It omits parameter context and offloads all parameter semantics to a bare schema; annotations cover safety but not invocation details.

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, and the description does not explain project_ref, its required status, or any of the beon_* context parameters. It adds no parameter meaning beyond the schema's type and format constraints.

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 specific verb ('Inspect') and resource ('database network allowlists'), clearly distinguishing it as a read-only tool. It does not explicitly name alternatives like supabase_update_network_restrictions or supabase_list_network_bans, so sibling differentiation is implicit rather than explicit.

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 when-to-use guidance, no exclusions, and no prerequisites. It implies inspection-only usage but does not tell the agent when to choose this over update_network_restrictions or list_network_bans.

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