import_data

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

No annotations are provided, so the description is the sole source. It discloses the expected structure and dry-run behavior but does not detail side effects, permissions, or conflict handling. Adequate but not exhaustive.

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 very concise—two sentences that state the purpose and explain the parameter. No wasted words; the key information is front-loaded.

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?

Given one parameter, no required fields, and an output schema, the description is mostly complete. It covers input structure and dry-run capability, though it could mention whether existing data is overwritten or appended.

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?

With 0% schema coverage, the description adds critical meaning: 'data' must be the full ExportData object with specific keys, and an empty dict triggers a dry-run. This goes beyond the schema's minimal definition of an optional object.

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 an ExportData blob produced by export_data. It specifies the verb ('import') and resource ('ExportData blob'), and distinguishes itself from the sibling export_data tool.

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 implies when to use: after exporting data with export_data. It mentions a dry-run option (pass empty dict), but does not explicitly exclude other scenarios. No alternative import tools exist among siblings, so guidance is clear.

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