import_records

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

Annotations are absent, so the description must carry the transparency burden. It does disclose that data must be a JSON array string including the record ID field and that a confirmation with the count is returned. However, it omits critical behavioral details such as whether existing records are overwritten, whether validation occurs, or permission requirements.

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 succinct, leading with a clear one-sentence purpose and using structured Args/Returns sections. Every sentence provides necessary information without redundancy.

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 tool with one parameter and an output schema, the description covers the main action, parameter format, and return value. It lacks details on side effects like overwriting and access requirements, but the overall description is reasonably complete for the tool's low complexity.

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 schema provides only the property name 'data' for the single parameter, but the description compensates fully by explaining that it is a JSON array string of records and that each record must include the project's record ID field. This adds meaningful semantics beyond the schema.

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 'Import records into the REDCap project,' using a specific verb and resource. It distinguishes from sibling import_* tools by focusing on records, though it doesn't explicitly contrast with related tools like import_repeating_instruments_events.

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?

There is no guidance on when to use this tool versus alternatives such as import_events, import_arms, or import_repeating_instruments_events. No exclusions, prerequisites, or preferred contexts are mentioned.

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