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

The description implies a read-only lookup but does not explicitly state side effects, permissions, or lack thereof. With no annotations, the description carries the full burden and only partially addresses behavior.

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 concise sentence with no redundancy. It directly conveys the core functionality without extraneous information.

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 lookup with two string parameters and no output schema, the description is sufficiently complete. It does not address potential output format or error handling, but these are not explicitly required.

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 description clarifies that 'value' is matched exactly and 'column' is the target column, adding some meaning beyond the schema. However, it does not provide details on allowed formats, enumerations, or edge cases.

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 returns rows where a column equals a value exactly, with case-insensitivity. It is specific about the operation but does not explicitly distinguish from sibling tools like dataset_search.

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?

No guidance is provided about when to use this tool versus alternatives. The description only states what it does, not when it should be preferred.

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