Query table with filter

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

With no annotations provided, the description carries the burden of disclosing behavior. It reveals that column and operator are validated against the real schema, and that results are limited to 200 rows. This provides meaningful operational context beyond the raw schema, though it does not detail error handling or return format.

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 two sentences with no superfluous content. It front-loads the core purpose and key constraints, making it quick to parse and directly informative.

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 moderate tool complexity (6 params, all documented in schema) and no output schema, the description adequately covers purpose, key limitation (single condition), validation behavior, and row limit. It omits explicit return format details, but for a row-returning query tool this is generally inferable.

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 parameters are fully documented. The description adds semantic value by explaining that column and operator are validated against the real schema, which clarifies execution behavior. It also contextually links column, operator, and value as a single WHERE condition.

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 action ('Select rows') and the specific scope ('from a table with a single WHERE condition'), which distinguishes it from sibling tools like join_tables or browse_table. The use of 'single WHERE condition' explicitly limits the tool's functionality, making its purpose unmistakable.

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 imparts clear context that this tool is for simple, single-condition queries without explicitly naming alternatives or exclusions. The phrase 'single WHERE condition' implies that more complex queries should use run_query or join_tables, but it does not state this directly.

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