batch_map_concepts_from_csv

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

With no annotations, the description bears full burden but only states the high-level action. It fails to disclose side effects (e.g., whether the input file is modified or deleted), resource requirements, error handling, or idempotency. Critical behavioral traits are missing.

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, well-formed sentence with no redundancy. It is front-loaded with the verb 'Process' and immediately identifies the resource. Every word contributes to understanding.

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?

The tool has one parameter, no annotations, and no output schema. The description does not specify the output CSV format, mapping logic (e.g., what concepts are mapped to), or error behavior. For a batch processing tool, this is insufficient for safe autonomous invocation.

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 single parameter csv_path is explained implicitly: 'Process a CSV file of keywords' clarifies it's a file path for a keyword CSV. However, with 0% schema description coverage, more detail is expected (e.g., allowed formats, absolute vs relative paths). The description adds minimal value beyond the schema itself.

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 processes a CSV of keywords, maps each row, and returns a CSV with appended results. It implies batch operation, distinguishing it from the sibling find_omop_concept (single concept lookup). However, it doesn't explicitly name the mapping target (e.g., OMOP concepts), slightly reducing precision.

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 the sibling find_omop_concept. There is no mention of prerequisites, ideal scenarios, or cases where this tool should be avoided. The agent receives no decision support.

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