check_timing_constraints

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

With no annotations, the description carries full burden for behavioral disclosure, but it only says 'run and parse' without explaining side effects, session requirements, whether the design must be synthesized/implemented first, or whether this is a read-only operation. The presence of an output schema covers return structure but not the behavioral context of executing a Vivado command.

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, which is efficient, but it is under-specified rather than concise. A few additional sentences about when to use the tool and what it requires would earn their place; as written, the description omits critical decision-making information.

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 having only one optional parameter and an output schema, the tool sits among many timing-related siblings and has no annotations. An agent needs more context about session prerequisites, what 'parse' means for the returned data, and how this differs from get_timing_summary or analyze_timing_closure to select and invoke it correctly.

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 schema description coverage is 0%, and the description does not explain the timeout_s parameter beyond its name. While the parameter is optional and self-explanatory, the description adds no meaningful semantics about default behavior, units, or consequences of setting a timeout.

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 names a specific verb ('run and parse') and a specific resource ('Vivado check_timing'), so an agent can tell this invokes the Vivado check_timing command. It does not explicitly differentiate itself from timing-related siblings like get_timing_summary or analyze_timing_closure, but the command name is specific enough to be unambiguous.

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 about when to call this tool versus alternatives such as get_timing_summary, get_timing_paths, or analyze_timing_closure. The description implies it runs a timing check, but does not state prerequisites like requiring an open project/session or a completed implementation run, nor does it exclude less appropriate contexts.

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