test_query

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

Discloses automatic LIMIT addition to prevent large result sets, a key behavioral trait. No annotations, so description carries burden; lacks explicit read-only or side-effect mention, but 'test' and 'preview' imply safety.

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?

Two-line purpose then bulleted args; no fluff. Front-loaded, every sentence valuable.

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?

Covers all parameters and behavior (auto LIMIT). Return mentioned as 'Query results preview'; output schema exists for details. Adequate for exploration tool with 3 params.

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 coverage is 0%, but description provides clear, concise explanations for all 3 parameters (database_id, query, limit). Adds meaning beyond schema types and default.

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?

Clear verb 'test' + resource 'SQL query' + context 'with automatic LIMIT (for exploration)'. Distinct from siblings like execute_query and explain_query.

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?

Explicitly mentions 'for exploration' and automatic LIMIT, implying use for testing/previewing rather than full execution. No explicit when-not or alternatives, but context with sibling names aids inference.

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