import_records

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

The description discloses that the tool appends data ('hängt an'), indicating an additive, non-destructive operation. However, with no annotations provided, it fails to disclose important behaviors such as validation, duplication handling, or error cases.

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, front-loaded sentence that efficiently communicates the core purpose without unnecessary words.

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 migration tool with complex nested objects and no annotations, the description is under-specified. It does not mention prerequisites, expected input format beyond 'parsed', side effects, or return behavior, leaving significant gaps for an AI agent.

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 mentions 'parsed entries' and 'optional releases' which map directly to the two schema parameters. The schema already provides detailed structural definitions, so the description adds only minimal semantic value beyond naming the parameters.

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 appends parsed entries and optionally releases to the store, using a specific verb and resource. The 'Migration' prefix provides context, but it does not explicitly differentiate from sibling tools like add_entry or create_release.

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 usage context is implied by the 'Migration' prefix, suggesting this tool is for bulk import after parsing. However, the description does not explicitly mention when to use it over alternatives like add_entry or preview_release, nor does it provide any exclusions.

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