set_simulation_top

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether the setting is persisted, what happens if the top module does not exist, or whether it mutates project state; for a configuration-setting tool this is a significant gap.

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 efficient sentence with the key action front-loaded. It earns its place but is arguably too sparse for a state-changing tool, which is better reflected in completeness than in conciseness.

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?

With no annotations, no output schema, and only 50% parameter documentation, the description is not complete enough for an agent to use this tool confidently. It omits prerequisites, error conditions, and the effect on subsequent simulation calls.

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 only 50%: fileset has a minimal default note ('default: sim_1') while top_module has no schema description at all. The tool description vaguely implies 'top_module' is the testbench module name but adds no format, naming expectations, or fileset interaction details beyond the schema.

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 gives a specific verb ('Set') and resource ('top-level testbench module for simulation'), so the tool's function is clear at a glance. It does not explicitly name or contrast with any sibling, but no sibling appears to share this exact purpose, making the intent easily distinguishable.

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?

There is no guidance on when to call this tool versus alternatives, nor any mention of prerequisites such as an open project, an existing fileset, or the relationship to launch_simulation/run_simulation. The agent must infer that this should be configured before simulation.

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