get_simulation_result

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the read/parse nature, but does not disclose that the timeout_s parameter may cause the tool to block or wait for simulation artifacts, nor does it explain behavior when logs or waveforms are missing. Important operational traits are left to inference.

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, front-loaded sentence with no filler. Every word contributes to the core purpose, and it is appropriately sized for a tool with two optional parameters and an output schema.

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?

While the output schema may cover return values, the description omits parameter semantics, usage timing, and behavior around timeout or missing artifacts. For a tool with two undocumented optional parameters and no annotations, this is insufficient context for reliable 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%, and the description does not mention simset or timeout_s at all. The agent receives no additional meaning beyond the bare parameter names. The description fails to compensate for the schema's lack of parameter documentation.

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 ('Read and parse') and names exact resources ('Vivado XSIM logs', 'generated waveform artifacts'). This clearly distinguishes it from sibling tools like run_behavioral_simulation or collect_report_bundle, which focus on running simulations or collecting build artifacts.

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 gives no guidance on when to call this tool versus alternatives such as get_workflow_trace_status or collect_report_bundle. It does not mention prerequisites like a previously run simulation or that this should be used after run_behavioral_simulation. Usage is only vaguely implied by the tool's name and description.

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