provision_neon_database

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

Without annotations, the description carries the transparency burden. It discloses mutating actions (create, apply schema, run migrations) and the requirement for an API key, but it does not describe side effects like cost, failure behavior, or what resources are affected. This is adequate but not rich.

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 two sentences, front-loaded with the main action, and wastes no words. It efficiently conveys purpose, capability, and a key prerequisite.

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?

Given the tool's complexity (8 parameters, side effects, no output schema), the description is too brief. It doesn't explain what the tool returns (e.g., connection string, project ID) or potential errors, which is critical for a provisioning tool. Missing details about ordering or interactions between parameters also reduce completeness.

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 100% coverage with descriptive parameter names and defaults. The description adds little beyond confirming that schema files and migration commands are supported, which is redundant with the schema. Baseline 3 is appropriate.

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 specifies a clear action—creating a serverless PostgreSQL database on Neon—and distinguishes it from sibling tools like provision_mongodb. It also mentions schema/migration support, so the agent knows the tool's core function.

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?

The description implies usage for provisioning a Neon database but does not explicitly state when to choose this over alternatives. It provides a prerequisite (Neon API key) and mentions schema/migration support, which offers some contextual guidance, but no explicit exclusion or alternative references.

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