create_project

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

No annotations are provided, so the description must carry the full behavioral disclosure burden. It only says a project is created from files; it does not mention whether an existing project is overwritten despite the force parameter, whether an active Vivado session is required, or what side effects occur on filesets.

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 filler and the action verb is front-loaded. However, it is quite sparse for a 17-parameter tool, so it earns high marks for brevity but not perfect marks for appropriate sizing.

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?

Despite an output schema, this is a high-complexity tool with 17 parameters, 5 required, a nested file_specs object, and 0% schema description coverage. The one-sentence description omits semantics for required parameters, nested schema structure, timeout behavior, force behavior, and how this tool connects to the broader Vivado workflow.

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 description coverage is 0% and the description adds almost no parameter meaning. It loosely maps to rtl_files, xdc_files, and sim_files by mentioning design, constraint, and simulation files, but it fails to explain required parameters like project_dir, part, top, or the complex file_specs object.

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 a specific action and resource: 'Create a Vivado project'. It also scopes the inputs as existing design, constraint, and simulation files, which clearly distinguishes this creation tool from siblings like open_project.

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 implies this is for creating a new project from existing files, but it does not explicitly state when to use it versus alternatives such as open_project or configure_simulation. Some context is present, but exclusions and alternate routing are left to inference.

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