run_pre_hw_signoff

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

No annotations are provided, so the description bears the full burden. 'Aggregate... into pre-hardware signoff' suggests a collection/read-like operation, but it does not disclose whether the tool writes artifacts, requires a project session, mutates state, or has side effects. This is a meaningful transparency gap for a signoff orchestration tool.

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?

One dense sentence with no filler, and the list of signoff domains is front-loaded. It could be better structured with a lead purpose statement and a separate parameter/usage note, but it is concise and each word adds scope 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 an output schema existing, this is a broad 10-parameter orchestration tool with no annotations and no usage context. The description leaves critical gaps: what inputs are required or optional, what prerequisites exist, what happens on failure, and how it relates to the many sibling report/audit tools. It is not complete enough for correct 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 provides no parameter-level meaning. None of the 10 properties (top, part, simset, fileset, run_name, timeout_s, project_dir, project_path, apply_waivers, report_manifest_path) are explained, and only indirect hints like 'reports' and 'waivers' appear. The description does not compensate for the low schema coverage.

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?

Description states a specific verb 'Aggregate' and a resource 'pre-hardware signoff', listing the domains drawn into it (source, elaboration, simulation, timing, CDC, power, reports, readiness, waivers). This is clear at a high level and distinguishes its comprehensive scope from narrower sibling tools, though it stops short of naming any sibling or saying how signoff is produced.

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 on when to run this tool instead of siblings such as run_project_audit, collect_report_bundle, or get_timing_summary. The phrase 'pre-hardware signoff' implies timing, but there is no explicit when-to-use, prerequisites, or exclusions.

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