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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the entire safety profile is covered structurally. The description adds nothing beyond the annotations - no pagination behavior, no scope of what 'configured' means, no auth/permission notes.

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 front-loaded sentence with no filler, which is structurally efficient. It is terse to the point of under-specification rather than wasteful, so it earns a good but not top conciseness score.

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-only list tool with 8 undocumented parameters, no output schema, and no explanation of pagination or filtering, the description leaves substantial gaps. Annotations cover the safety profile, but the agent still lacks enough information to call it confidently on the non-obvious parameters.

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, including required project_ref and a set of opaque beon_* parameters (beon_context, beon_environment, beon_connection_id). The description supplies no parameter meaning whatsoever, leaving the agent with no explanation of what must be supplied.

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 and resource ("List configured SAML identity provider metadata"), which cleanly separates it from singular siblings like supabase_get_sso_provider and mutating ones like supabase_create/update/delete_sso_provider. It never names those siblings explicitly, so the distinction is inferred rather than stated.

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 exclusions, and no mention of the related siblings (get/create/update/delete_sso_provider). The agent must infer from the verb alone that this is the enumeration variant.

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