query

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

The annotation readOnlyHint is reinforced and expanded by the description's mention of read-only mode and SELECT-only restriction. It adds specific behavior like max-rows default, cross-source joins, and pagination support. No contradiction; the description goes beyond the annotation by disclosing default limits and mode.

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?

Three sentences deliver a clear purpose, constraints, and pagination details with no wasted words. The description is front-loaded with the main function and includes all key behavioral notes in a compact, structured way.

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 the tool's complexity (6 params, no output schema), the description covers essential context: data source registration, DuckDB, read-only mode, max rows, pagination, and cross-source joins. It doesn't detail error handling or exact return format, but that's partially covered by the mention of row limits and the sibling tools provide supplementary context.

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 100%, so all parameters are individually documented. The description adds valuable context beyond the schema: clarifies source='_all' for cross-source joins, confirms limit/offset are for pagination, and explains max_rows as an override. This extra meaning helps the agent use the parameters correctly.

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 executes a SQL query against a registered data source using DuckDB, distinguishing it from sibling tools like list_sources or get_schema. The verb 'Execute' and resource 'SQL query' are specific and unambiguous.

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?

It provides explicit context: default read-only mode, only SELECT allowed, and how to use source='_all' for cross-source joins. It also mentions pagination via limit/offset. It doesn't explicitly enumerate when not to use or compare with alternatives, but the context is clear enough for an agent to decide.

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