parse_sim_log

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it does so well: it calls out non-auto-detection, bounded evidence sampling, exclusion of compile/elaboration logs, and the automatic inclusion of about 100 lines of context for the first group. It does not discuss output shape or error behavior in depth, but the disclosed behaviors are meaningful and specific.

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?

Three dense sentences deliver the core purpose first, then key caveats, then routing advice. Every sentence contributes new information, and none of the schema's parameter descriptions are redundantly restated.

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 there is no output schema, the description helpfully names and explains two output-related concepts (candidate_previous_logs and first_group_context) and points to get_error_context for richer context on other groups. It is complete enough for an agent to understand what the tool returns and how to use it, though a bit more about the overall result structure would make it fully self-sufficient.

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 input schema already describes all five parameters with 100% coverage, so the baseline is 3. The description adds context beyond the schema by explaining that simulator is not auto-detected and that first_group_context is automatically populated, which is helpful, but it does not need to repeat parameter definitions.

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 states a specific verb ('Parse'), the exact resource (VCS or Xcelium simulation log), and the specific output (grouped runtime failures by signature). It also differentiates itself from sibling tools by noting that get_error_context should be used for other error groups, making the purpose unmistakable.

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 clearly indicates that the simulator argument is required and not auto-detected, which prevents a common misconfiguration. It also says candidate_previous_logs excludes compile/elaboration logs and directs users to get_error_context for non-first groups, giving practical routing guidance, though it could more explicitly state when to prefer this tool over analyze_failures or diff_sim_failure_results.

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