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

With no annotations, the description must disclose behavior on its own. It states the matching condition (case-insensitive equality) but does not mention whether multiple rows can be returned, if there are result limits, ordering, or error handling when no matches occur. It is not misleading, but it is far from a transparent account of the tool's runtime 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, compact sentence that conveys the core functionality without extraneous words. It is well-structured and front-loads the dataset name and operation, making it easy to scan. No redundancy or unnecessary detail.

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 simple schema (two strings) and the presence of sibling tools, the description adequately conveys the basic lookup operation. It differentiates from search by emphasizing 'exactly', but it does not mention return cardinality, limits, or when to prefer this over a broader search. It is sufficient for a trivial tool but lacks context to fully disambiguate all use cases.

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 the 'value' parameter is matched case-insensitively and 'exactly', which adds semantics beyond the schema. However, it does not explain what 'column' refers to (e.g., column name format, whether it must exist) or that both parameters are required to perform a lookup. It provides partial enrichment but leaves gaps.

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 that the tool returns rows where a column equals a provided value, and explicitly notes case-insensitivity. The title reinforces the 'exact key' intent, distinguishing it from search-like tools. However, the description is phrased passively ('The rows... where a column equals') rather than as a direct command, and does not explicitly name the dataset as 'Patientvo' in a way that clarifies the resource being queried.

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 on when to use this tool versus its alternatives (e.g., dataset_search for partial matches, dataset_top for ranked rows). There is no mention of prerequisites, limitations, or scenarios where this tool is preferred. The description gives no actionable direction for selecting this over siblings.

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