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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: it doesn't explain what 'eligibility' means, whether it requires approval, or what the inspection entails.

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?

It is a single front-loaded sentence with zero padding, which is structurally efficient. The brevity is also its weakness, but as structure it is clean and earned.

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 a read operation with eight parameters (seven opaque beon_* fields), no output schema, and no sibling differentiation, this one-liner is far too thin. An agent cannot determine intent, side effects on the undocumented metadata params, or how results differ from get_upgrade_status.

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?

There are 8 parameters with 0% schema description coverage, so the schema provides no help and the description must compensate. It says nothing about any parameter — not even the required project_ref, nor the seven undocumented beon_* metadata fields — leaving the input contract effectively unexplained.

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 description states a specific verb (Inspect) and resource (database upgrade eligibility), which is clearer than a tautology. However, it offers no differentiation from the closely related sibling supabase_get_upgrade_status, leaving the agent to guess which to call for eligibility vs. status questions.

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, no prerequisites, and no mention of alternatives such as supabase_get_upgrade_status. The agent receives a purpose but no context for selecting this tool over its sibling.

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