WayStation MCP Server

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 states 'read-only' which is helpful, but doesn't mention important behavioral aspects like authentication requirements, rate limits, query timeout policies, result format, error handling, or whether it supports parameterized queries. For a database query tool with zero annotation coverage, this leaves significant gaps.

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 extremely concise (one sentence) and front-loaded with all essential information. Every word earns its place with no wasted text, making it easy for an agent to parse quickly while still conveying the core functionality.

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 database query execution tool with no annotations and no output schema, the description is insufficiently complete. It doesn't describe the return format (rows, columns, structure), error conditions, performance characteristics, or any constraints on the SQL that can be executed. The 'read-only' hint is helpful but doesn't compensate for the missing behavioral context needed for effective tool use.

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?

Schema description coverage is 100% with the single 'query' parameter well-documented in the schema. The description doesn't add any additional parameter information beyond what's in the schema, but since schema coverage is complete, the baseline score of 3 is appropriate. No value is added beyond the structured data.

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 action ('executes a read-only SQL query') and target resource ('against your Neon database'), making the purpose immediately understandable. It distinguishes from some siblings like 'executePostgreSQLSqlQuery' by specifying the database type, though it doesn't explicitly differentiate from 'fetchNeonSchema' which has a different purpose.

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 provides minimal guidance on when to use this tool. It mentions 'read-only' which helps differentiate from write operations, but doesn't specify when to choose this over 'executePostgreSQLSqlQuery' or 'executeSupabaseSqlQuery' (other SQL execution tools) or when to use 'fetchNeonSchema' instead for schema queries. No explicit alternatives or exclusions are provided.

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