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

With no annotations, the description carries the full burden. It discloses a key behavioral trait: matching is exact but case-insensitive. However, it doesn't clarify behavior for multiple matches, no matches, or the exact structure of the returned data, leaving meaningful gaps.

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 focused sentence with no filler, front-loading the core behavior. Every word contributes value, making it both concise and efficient for an agent to parse.

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 2-parameter tool with no annotations and no output schema, the description is reasonably complete but leaves ambiguity: the title says 'a row' while the description says 'rows', and the return format is unspecified. It could also clarify how it differs from dataset_top or dataset_provenance.

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%, but the description references the parameters by name ('column', 'value') and explains their relationship. It adds the case-insensitive matching semantic, which is meaningful, but does not fully elaborate parameter semantics beyond what schema names and types already suggest.

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 a precise behavior: returning rows where a column exactly equals a value, explicitly noting case-insensitivity. The title and description together make it distinct from sibling tools like dataset_search, which likely performs fuzzy or broader matching.

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 the tool is for exact case-insensitive lookups, which hints at when to choose it over dataset_search, but it never explicitly states when to use it versus alternatives or when not to use it. The guidance is only implied, not spelled out.

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