collect_report_bundle

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

With no annotations, the description must disclose behavioral traits itself. It mentions the destination directory and manifest file, but it does not state whether the tool triggers Vivado, requires an existing project, overwrites prior outputs, or has side effects beyond writing reports. This leaves significant invocation risk for the agent.

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 sentence with no filler and a front-loaded action verb. It is appropriately short, though the brevity comes at the cost of parameter and behavior detail.

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 parameter descriptions, and several overlapping sibling tools, this description is insufficient for correct tool selection and invocation. The output schema covers return values, but the missing behavioral and parameter context leaves important gaps.

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 explain run_name, timeout_s, or report_dir. The references to vmcp_reports and report_manifest.json hint at where outputs land but do not clarify parameter meaning, defaults, or constraints, so the agent cannot confidently populate the optional parameters.

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 identifies a specific action ('Generate and collect'), a specific resource ('pre-hardware Vivado reports'), and concrete outputs ('vmcp_reports with report_manifest.json'). It is clear enough to distinguish the tool from generic collection tools, though it does not explicitly contrast it with similar siblings like collect_build_artifacts or collect_diagnostic_bundle.

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 provides no explicit guidance on when to use this tool versus alternatives. 'Pre-hardware' gives some temporal context, but there is no mention of when not to use it or how it relates to collect_build_artifacts, collect_diagnostic_bundle, or run_pre_hw_signoff.

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