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

With no annotations provided, the description carries the full burden of behavioral disclosure. It covers idempotency via CREATE TABLE IF NOT EXISTS, declares a successful re-run harmless, describes the per-step return value, explains error surfacing behavior, and notes the nsec-signed proof requirement. This is unusually transparent.

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?

The description is information-dense but not bloated. Every sentence adds value: purpose, trigger condition, idempotency, return/error behavior, and access restriction. The key facts are front-loaded in the first line.

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 restricted diagnostic/recovery tool, the description covers the key operational context: when to run it, why it is safe, what it returns, how errors surface, and who is allowed to invoke it. An output schema exists, so the return value does not need further elaboration.

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?

The input schema has 0% description coverage, and the description does not explicitly explain the dpop_token parameter or how it maps to the nsec-signed proof requirement. The auth-related context in the description adds some meaning, but the agent still has to infer that dpop_token is the credential/proof token.

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 opens with a specific verb and resource: 'Re-run ensure_schema() on every NeonVault'. It clearly frames the tool as a diagnostic/recovery tool for persistent 4xx errors and suspected schema/grants problems, which distinguishes it from sibling tools like restore_credits or reset_pricing_model.

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 an explicit trigger scenario: 'Neon HTTP SQL API is returning persistent 4xx errors and the operator suspects the schema isn't there or grants are wrong.' It does not name alternative tools or state when not to use it, but the context is clear enough to guide selection.

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