project_open

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

No annotations are provided, so the description must carry the full burden of disclosing behavioral traits. 'Load an existing project into the session' implies a mutation of the current session state, but it does not disclose side effects such as whether unsaved changes are discarded, whether the current project is replaced, or whether any confirmation is required. Without such disclosure, an agent cannot anticipate the impact of this action.

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 and well-structured: a one-sentence purpose statement followed by an Args section. It is front-loaded with the core action and resource, and the parameter documentation is inline. No unnecessary words. It could be slightly more structured (e.g., bullet points), but it is efficient and clear.

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?

While an output schema exists (so return values are covered), the description is missing important contextual information for a project-loading operation. It does not mention what happens to the current project state, whether the load is destructive, or what prerequisites exist (e.g., must the project file be valid). Given the operation is a fundamental session change, this lack of behavioral context is a significant gap, especially compared to richer descriptions of sibling tools.

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 only provides the parameter name 'Project Path' with no description (schema coverage 0%). The description adds meaning by stating the parameter is 'Path to an existing project file' and clarifies the expected format (.kdenlive-cli.json). This goes beyond the bare schema, though it does not elaborate on path resolution, validation, or acceptable file extensions. Given the minimal schema, this is a modest but useful enrichment.

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 'Load' and the specific resource 'an existing .kdenlive-cli.json project' and the destination 'into the session'. This is specific and distinct from sibling operations like project_new (which creates a project) and project_save (which persists the current project). The phrase 'existing' implicitly differentiates it from project_new, and the file format adds precision.

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 no guidance on when to use this tool versus alternatives. It does not mention that this is for loading a previously saved project, or that project_new is for creating a blank project, or that project_save is for persisting changes. In a toolset with many project-related operations, this omission leaves the agent to infer usage context from the tool name alone.

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