gui_import_file

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

No annotations are present, so the description carries full burden. It only states it opens a dialog, without mentioning side effects, blocking behavior, or return values. The tool's output schema exists but is not described, leaving behavioral expectations unclear.

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 concise sentence with no extraneous information. It is front-loaded with the core action. However, it could be slightly expanded to include critical missing details 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's simplicity (one parameter, output schema exists), the description omits important context such as whether the dialog is modal, what the tool returns, and how it interacts with the user. The output schema is not mentioned, so the agent lacks a complete picture.

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 schema has 0% coverage for descriptions, so the tool description adds value by specifying that 'path' is a file path and providing examples (.apkg/.csv). This clarifies the parameter's format beyond the schema's bare 'Path' title, though more detail (e.g., absolute vs relative) would improve it.

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 it opens Anki's import dialog for a given file path, with examples of file types (.apkg/.csv). It distinguishes from other sibling tools like import_package which likely imports without GUI. However, it could be more precise about the tool's exact action (e.g., does it actually import the file or just open the dialog?).

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 such as import_package (non-GUI import) or gui_add_cards. The description does not specify 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.