import_litchi

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

With no annotations, the description carries full burden. It discloses key behaviors: parsing the CSV and automatically saving to the account. However, it omits details on validation errors, required CSV columns, or whether existing missions might be overwritten, which are important for a mutation tool.

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 with three short sentences that front-load the main action. Every sentence adds value: purpose, format details, and auto-save behavior. No wasted 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?

Given the tool's moderate complexity and lack of output schema, the description covers the core purpose and behavior but lacks information on error handling, required CSV structure, and potential conflicts with existing missions. It is adequate but not comprehensive.

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 coverage is 100%, so baseline is 3. The description adds context about the CSV format being parsed and the mission creation, but does not elaborate on expected CSV columns or validation rules. This meets the baseline but does not substantially enhance parameter understanding.

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 verb 'Import' and resource 'Litchi CSV file', explicitly specifying the outcome 'create a new waypoint mission'. It distinguishes itself from siblings like 'create_mission' by focusing on the specific Litchi CSV format.

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 provides clear context for when to use this tool: when you have a Litchi CSV file to import. It does not explicitly list exclusions or alternatives, but the purpose is obvious given the tool name and description, and it stands apart from mission creation tools.

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