import_events

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

With no annotations, the description must carry the full burden. It discloses a key destructive behavior: 'If True, existing events not in the import will be deleted' for the override parameter. However, it doesn't mention other side effects like idempotency, impact on project structure, or potential irreversibility beyond the override.

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 follows a clear, conventional structure: summary line, Args section, and Returns section. Every sentence adds value with no redundancy or fluff.

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 only two parameters and an output schema, the description covers purpose, both parameters, and return value adequately. It lacks mention of alternatives and doesn't enumerate all fields in the data array, but remains complete for the tool's 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?

Schema description coverage is 0%, so the description is the only source for parameter meaning. It explains data as 'JSON array of event objects with event_name, arm_num, day_offset, etc.' and clarifies override's deletion behavior. However, the 'etc.' is vague and doesn't list all required fields or provide examples.

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?

Description states 'Import (create or update) events in a longitudinal REDCap project' with a specific verb and resource, clearly identifying the tool's action. It distinguishes from siblings like export_events and delete_events by emphasizing the create/update nature, though it doesn't explicitly name alternatives.

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 gives no explicit guidance on when to use this tool versus alternatives such as export_events or delete_events, nor does it mention when not to use it. Usage is only implied by the verb 'import'.

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