Query properties (SQL)

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

With no annotations provided, the description fully discloses the safety behavior: only single SELECT statements are accepted, leading WITH/CTE is allowed, mutating and file/extension keywords are rejected, and results are capped at 1000 rows. This gives an agent strong grounding for safe invocation.

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 compact and front-loaded with the core purpose, followed by a clearly labeled SAFETY section. Every sentence earns its place, and the keyword list is necessary for correct use of a SQL query tool.

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?

Despite having no output schema, the description tells the agent what table to query, how to discover columns, what SQL is permitted, and the hard row limit. This is sufficient for an agent to select and invoke the tool correctly without additional documentation.

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 input schema already covers all parameters at 100%, so the baseline is 3. The description adds meaningful semantic detail about the sql parameter's allowed statement form and rejection keywords, and reinforces the limit parameter's enforced cap, going slightly beyond the schema.

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 read-only SQL SELECT against a county's 'properties' view, backed by embedded DuckDB. It names the specific resource and includes a pointer to getPropertyQuerySchema for columns, helping distinguish it from sibling query tools like queryPlaces and queryPermits.

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 a clear prerequisite: use getPropertyQuerySchema first to see available columns. It also establishes the scope of use by restricting queries to a single read-only SELECT over the properties table, though it does not explicitly enumerate when to prefer sibling tools.

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