import_project

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It fails to specify whether the import creates a new project, merges with the current one, requires specific file types, or has any side effects, leaving the agent without critical safety and execution context.

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 in length—one short sentence—but the brevity comes at the cost of substance. It is front-loaded but under-specified, so it is not 'appropriately sized' for a tool with no annotation support.

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 a low-complexity schema but no output schema and no annotations, the description should provide substantial context. It does not explain the import behavior, file compatibility, or relationship to sibling tools, making the description incomplete for safe and correct invocation.

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 input schema has zero description coverage, and the description adds no meaning beyond repeating the parameter name. The single 'file_path' parameter is not clarified regarding accepted formats, file extension requirements, or how the path should be provided.

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 states the action 'Import a project' and source 'from a file', which is clear for a basic verb+resource structure. However, it does not distinguish this from sibling tools like load_project or import_timeline_from_file, which could easily overlap in purpose.

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 given on when to use this tool versus alternatives. The description does not mention any prerequisites, file format expectations, or why one would choose import_project over load_project or import_timeline_from_file.

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