import_repeating_instruments_events

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

With no annotations, the description carries the burden. It states that it creates or updates, returns an error on older instances, and returns a confirmation message with a count. However, it does not disclose whether the operation replaces or merges existing configuration, or any permissions needed. This is acceptable but leaves behavioral gaps.

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 concise and well-structured, with a clear purpose statement, version note, Args, and Returns sections. Every sentence serves a purpose without unnecessary fluff, making it easy to parse.

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 tool with a single parameter and no annotations, the description covers the operation, parameter format, return value, and an error condition. It lacks details on merge/replace semantics, but given the simplicity, it is reasonably complete. The presence of an output schema (though not shown) shifts some burden, but the description still provides essential context.

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 input schema has 0% description coverage, so the description must compensate. It does this excellently by explaining that 'data' is a JSON array of objects with event_name, form_name, and custom_form_label fields, adding critical meaning beyond the bare schema definition.

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 imports (creates or updates) repeating instruments and events configuration, specifying the exact resource. This distinguishes it from sibling tools like import_records, import_events, import_arms, etc., by focusing on the 'repeating instruments and events' aspect.

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 description includes a version requirement ('Requires REDCap 6.16 or later') which gives some usage context, but it does not explicitly state when to use this tool versus alternatives or provide exclusion criteria. The purpose implies usage for configuring repeating instruments, but no direct guidance is given.

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