export_query

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

The description discloses truncation behavior for large results, but with no annotations, it should also note that the tool is read-only (SELECT), how truncation is indicated, and the default maxChars limit. It does not mention potential error states or rate limits.

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 sentence that is concise and front-loaded with the core action. However, it could be slightly more informative without losing conciseness, e.g., by noting the maxChars parameter.

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 5 parameters and no output schema, the description is incomplete. It lacks details on output format, truncation handling, parameter use, and error scenarios. More context is needed for an agent to use this tool effectively.

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 description adds no meaning beyond the input schema. It does not explain that 'params' are for parameterized queries or that 'maxChars' controls the truncation character limit. Only 'sql' is mentioned implicitly via 'SELECT'. Schema coverage is 40%, but the description fails to compensate for undocumented parameters.

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 runs a SELECT query and returns truncated JSON for large results. However, it could better distinguish from sibling query tools like 'query' or 'query_one' by explicitly noting that it is designed for large results and returns JSON rather than raw result sets.

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 no guidance on when to use this tool vs alternatives, such as 'query' for small results or 'export_query' for large datasets. It does not mention 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.