query

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

No annotations provided, but the description details supported DuckDB SQL features (JOINs, window functions) and prerequisites. It does not mention error handling or performance impacts, but is fairly transparent.

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?

Concise at a few sentences with main purpose front-loaded. Every sentence adds value without verbosity.

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 an output schema exists (not needed to explain return values), the description covers prerequisites, capabilities, and usage context thoroughly.

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% (no parameter descriptions in schema). The description explains the sql parameter well ('Supports full DuckDB SQL'), but the limit parameter receives no additional explanation beyond its existence.

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 'Execute a SQL query against loaded MCAP data', specifying the verb and resource. It distinguishes from siblings like load_recording and list_recordings.

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 states data must be loaded first via load_recording, and instructs to call load_recording if a table is missing. Provides context on supported SQL features.

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