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

With no annotations, the description carries the behavioral burden. It usefully discloses case-insensitive exact matching, but it does not state whether a single row or all matching rows are returned, how results are ordered or limited, or what happens when no row matches. The singular title ('a row') and plural description ('rows') leave cardinality ambiguous.

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, front-loaded sentence with no filler. 'The rows ... where a column equals a value exactly (case-insensitive)' delivers the core operation and matching behavior in thirteen words.

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 two-parameter lookup with no output schema and no annotations, the description covers the match predicate but leaves the result shape, multiplicity, and edge-case behavior unspecified. It is adequate for a simple tool but not fully complete: an agent cannot predict whether the call returns one row or many, or what the payload looks like.

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 0%, so the description must give meaning to 'column' and 'value.' It does: 'where a column equals a value exactly.' This maps both parameters to their lookup roles, but it does not clarify data types, accepted column-name format, or value syntax beyond what the schema's minLength constraints imply.

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 title and description clearly identify an exact-match row lookup: 'Look a row up by an exact key' and 'rows ... where a column equals a value exactly.' The 'exactly (case-insensitive)' wording distinguishes it from fuzzy or partial search, though it does not name sibling tools explicitly.

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 exact-match/case-insensitive framing implies this is for looking up rows by an exact value rather than searching or stats, but the description gives no explicit when-to-use guidance, exclusions, or references to alternatives such as dataset_search. Usage context must be inferred by the agent.

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