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

With no annotations provided, the description must carry the behavioral burden. It discloses that matching is case-insensitive, which is useful, but it omits other behavioral traits such as whether multiple rows can be returned, pagination, ordering, or error behavior. The plural 'rows' suggests multiple results, but this is not explicit.

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 a single sentence with no redundant words. It is front-loaded with the core purpose and includes the key detail of case-insensitivity. No fluff or unnecessary elaboration.

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?

For a simple two-parameter lookup tool with no output schema or annotations, the description is adequate but not complete. It clarifies the matching semantics but leaves ambiguity about whether one or multiple rows are returned, and it does not mention limits or response format. This is a minimal viable description but lacks several practical details.

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 description coverage is 0%, so the description must compensate for the absence of parameter details. It only says 'a column equals a value,' which maps directly to the parameter names but adds no extra meaning about formats, constraints, or valid inputs. The names 'column' and 'value' are somewhat self-explanatory, but the description does not clarify expected types or examples.

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 states what the tool does: it returns rows where a column equals a value exactly, with case-insensitive matching. This is specific and distinguishes it from a fuzzy search tool like dataset_search, though it lacks a strong verb (e.g., 'returns') and reads as a noun phrase rather than an action.

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?

There is no guidance on when to use this tool versus alternatives like dataset_search. It does not mention exclusions, prerequisites, or typical use cases. The only implied context is exact-match lookups, but it never explicitly contrasts with fuzzy or partial matching.

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