find_rows

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds crucial context: filtering is performed client-side (implying all rows may be fetched), and explains the predicate DSL format and operators. This goes beyond annotations.

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 concise (3 sentences) and efficiently communicates key material. It front-loads the core purpose and DSL format. Could be slightly more structured but is effective.

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 schema covers all parameters, annotations are present, and there is no output schema, the description sufficiently explains the filtering mechanism. It is complete for a client-side filtering tool, though adding a note about potential large data transfer due to client-side filtering would enhance completeness.

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% and all parameters have descriptions. The description adds meaning to the 'where' parameter by providing DSL syntax and operators. Other parameters (table, page, page_size, order_by, direction) are adequately described in 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 finds rows using a predicate DSL and specifies it is client-side filtering. It includes the DSL format and operators, which distinguishes it from list_rows (simple listing), search_rows (full-text search), and query_sql (direct SQL). However, it does not explicitly contrast with siblings like list_rows or search_rows.

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 implies when to use this tool (when predicate-based filtering is needed) but does not explicitly state when not to use it or provide alternatives. With siblings like list_rows, search_rows, and query_sql, clearer guidance would help.

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