aedt_import_dataset

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

No annotations are provided, so the description must fully explain behavior. It only states the high-level action without disclosing side effects (e.g., whether existing datasets are overwritten), required permissions, error handling, or return value details. The lack of behavioral context is a significant gap.

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 (single sentence) and front-loaded, but it is overly brief, sacrificing clarity for brevity. It could be expanded with useful detail without becoming verbose.

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 the tool has 6 parameters, no output schema described in the description (though output schema exists in context), and no annotations, the description is severely incomplete. An agent cannot determine required inputs, output format, or behavior from this description alone.

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 description coverage, the description should explain key parameters. It only mentions '1D or 3D' which loosely relates to the 'dimensions' parameter, but does not explain 'input_file', 'name', 'is_project_dataset', 'sort', or 'encoding'. The description adds minimal semantic value 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 the action (import) and resource (1D or 3D dataset file) and differentiates from sibling tools like aedt_create_dataset, which creates datasets rather than importing from files. However, it does not specify the file formats supported.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it does not explain how this differs from aedt_create_dataset or aedt_read_design_data. There is no mention of prerequisites or context for use.

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