vivado_create_project

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

With no annotations, the description must disclose behavioral traits but only says 'in the managed session', which is vague. It doesn't mention side effects, whether it requires an active session, default behaviors (e.g., handling existing projects), or the meaning of the 'force' parameter.

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 (12 words), but it is under-specified for a tool with 7 parameters. Conciseness should not come at the cost of missing essential details; a longer description with key parameter clarifications would be more helpful.

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 complexity (7 parameters, output schema exists), the description is severely incomplete. It does not explain what 'Project Mode' means, what the output contains, or any prerequisites. The output schema is mentioned in signals but not referenced in the description to aid understanding.

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%, so the description must compensate by explaining key parameters. However, it adds no information beyond the parameter names. The parameters like 'part', 'board_part', 'force' are not explained, leaving the agent to guess their roles.

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 action 'Create' and the resource 'Vivado Project Mode project', with context 'in the managed session'. This distinguishes it from siblings like vivado_open_project (opens existing) and vivado_start_session (starts session). However, it lacks specificity about what 'Project Mode' entails compared to other modes.

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 like vivado_open_project, vivado_start_session, or vivado_source_tcl. It does not mention prerequisites (e.g., an active session) or scenarios where this tool is appropriate.

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