verilog_simulate

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

No annotations are provided, so the description carries the full behavioral burden. It discloses meaningful non-obvious behaviors: capturing $fatal runtime assertions, detecting testbench errors, and enforcing a timeout to prevent infinite loops. This is strong value beyond the schema.

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 well-structured sentence with no filler. It leads with the primary action, then adds the most important behavioral safeguards, making it easy to parse quickly.

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?

The description covers the core simulation behavior and timeout safeguard, but with no output schema and no annotations, it does not explain what the tool returns or how the captured assertions/errors are presented to the agent. It also lacks explicit sibling differentiation.

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 100%, so all parameters are already documented. The description adds minimal parameter-level nuance, mainly connecting timeout_ms to infinite-loop protection. This meets the baseline but does not exceed it.

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 construct: 'Compiles and runs a behavioral testbench simulation using iverilog + vvp.' This clearly identifies what the tool does and distinguishes it from the sibling lint/compile tools.

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 purpose implies this is the tool to use when simulation is needed, but it never explicitly states when to choose it over verilog_compile or verilog_lint. There is no when-to-use, when-not-to-use, or alternative routing.

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