WayStation MCP Server

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

No annotations are provided, so the description carries full burden. It states it 'fetches' schema, implying a read-only operation, but doesn't disclose behavioral traits like whether it requires specific permissions, returns structured data, has rate limits, or handles errors. The description is minimal and lacks crucial operational context for a tool with no annotation coverage.

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, efficient sentence that front-loads the core purpose ('Fetches the schema...') and adds specific detail ('showing tables and columns'). There is no wasted verbiage, and every word contributes to understanding the tool's function.

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 no annotations and no output schema, the description is incomplete for a tool that likely returns complex schema data. It mentions 'tables and columns' but doesn't describe the return format, structure, or any metadata. For a schema-fetching tool with zero structured coverage, this minimal description leaves significant gaps in understanding how to interpret results.

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 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add parameter semantics, but that's appropriate here. Baseline is 4 for zero parameters, as the schema fully covers the input requirements without requiring descriptive compensation.

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 verb ('fetches') and resource ('schema of the connected Neon database'), specifying what it shows ('tables and columns'). It distinguishes from siblings like fetchPostgreSQLSchema by naming the specific database system (Neon), but doesn't explicitly contrast with other schema-fetching tools beyond that implicit differentiation.

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 retrieving database schema information, which is clear from context. However, it provides no explicit guidance on when to use this tool versus alternatives (e.g., fetchPostgreSQLSchema, fetchSupabaseSchema, or executeNeonSqlQuery for schema queries), nor any prerequisites or exclusions.

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