Combined MCP Server

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

With no annotations provided, the description carries full burden and does well by disclosing critical behavioral traits: the 100-row limit for direct returns, S3 storage for larger results, and authentication requirements via get_cluster_credentials. However, it doesn't mention rate limits, timeout behavior, or error handling for malformed queries.

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 efficiently structured with a clear purpose statement followed by important behavioral information, then parameter explanations. Every sentence adds value, and the Args section is appropriately formatted without redundancy.

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 this is a database query execution tool with no annotations but with an output schema, the description provides good coverage of purpose, behavior, and parameters. However, it could better address error scenarios, performance characteristics, and how to retrieve full results from S3 when applicable.

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?

With 0% schema description coverage, the description compensates well by explaining all three parameters: sql (the query to execute), db_user (for authentication), and db_group (optional permissions). It adds meaningful context about authentication via get_cluster_credentials that isn't in the schema.

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 specific action ('Execute a SQL query') and target resource ('on Redshift'), distinguishing it from sibling tools like query_vectorstore or describe_table. It provides precise verb+resource information that helps the agent understand this is a database query execution tool.

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 SQL query execution on Redshift, but doesn't explicitly state when to use this tool versus alternatives like query_vectorstore or describe_table. There's no guidance on prerequisites, error conditions, or specific scenarios where this tool is preferred over siblings.

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