fetchNeonSchema

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

No annotations are provided, so the description must fully disclose behavioral traits. It indicates a read-only fetch via 'Fetches' and mentions 'tables and columns' as output, but it does not explicitly confirm read-only behavior, describe side effects, permissions, or error conditions. This leaves a significant transparency gap.

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 a single, front-loaded sentence with no redundant or extraneous words. It efficiently states the action and the resource.

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 simplicity (no parameters, no annotations, no output schema), the description is reasonably complete: it identifies the connected Neon database and what the schema shows. However, it could have specified the return format more explicitly or clarified that it reflects the currently connected database, so it's not perfect but adequate.

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 tool has zero parameters and the input schema is empty, so schema coverage is 100% vacuously. Per guidelines, the baseline for 0 params is 4. The description adds slight value by hinting at the output contents ('tables and columns'), but no parameter explanation is needed.

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 uses a specific verb ('Fetches') and resource ('schema of the connected Neon database') with additional detail ('showing tables and columns'). It clearly differentiates from sibling tools like fetchPostgreSQLSchema and fetchSupabaseSchema by explicitly naming Neon.

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 context via 'connected Neon database' but does not explicitly state when to use this tool over alternatives such as fetchPostgreSQLSchema or fetchSupabaseSchema, nor does it mention any exclusions. Usage guidance is implied rather than spelled out.

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