fetchNeonSchema

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

With no annotations, the description carries the burden of conveying safety. The verb 'fetches' implies a read-only operation, and 'showing tables and columns' indicates the output. However, it does not explicitly state that the operation is non-destructive, does not require specific permissions, or describe any side effects, though these are unlikely for a schema fetch.

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, well-structured sentence that front-loads the action ('Fetches the schema') and provides relevant specifics without unnecessary words.

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 simple read-only tool with no parameters, the description adequately conveys the tool's purpose and output. However, it does not describe the exact return format or mention any limitations (e.g., which schema is inspected), though this may not be critical given the tool's simplicity.

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 no parameters, so the description doesn't need to explain any. The input schema is empty, and the description's mention of 'tables and columns' provides context for what the schema output contains, but no parameter details are 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 clearly states the tool fetches the schema of the connected Neon database and explicitly mentions the output (tables and columns). This distinguishes it from sibling tools like fetchPostgreSQLSchema and fetchSupabaseSchema by specifying the Neon context.

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 the tool is for fetching schemas from a Neon database, but it does not provide explicit guidance on when to choose this over alternative schema-fetching tools (e.g., fetchPostgreSQLSchema) or mention exclusions. The usage context is clear but not explicitly differentiated.

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