vivado_run_implementation

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

No annotations exist, so the description must disclose behavioral traits. It mentions 'wait' (implying blocking) but fails to describe timeout behavior, resource usage, potential side effects, or that synthesis must precede implementation. The description is insufficient.

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 extremely short (one sentence) but sacrifices necessary detail for conciseness. It does not efficiently convey information beyond the tool's core purpose.

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 4 parameters, no annotations, and an output schema (not shown), the description is severely incomplete. It omits prerequisites (e.g., prior synthesis), parameter roles, behavioral implications, and output format, making it inadequate for safe agent 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?

Schema description coverage is 0% (no parameter descriptions) and the tool description adds no explanation of any of the four parameters (session_ref, run_name, jobs, timeout_seconds). The agent cannot understand parameter meanings or defaults from the description.

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 uses a specific verb-resource pair ('Launch and wait for a Vivado implementation run'), clearly distinguishing it from sibling tools like vivado_run_synthesis and vivado_generate_bitstream.

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 provided on when to use this tool versus alternatives such as vivado_run_synthesis or vivado_generate_bitstream. There is no mention of prerequisites or context for invocation.

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