generate_hardware_spec_tool

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful scope context ('vendor-neutral') and the domains included, but it does not disclose additional behavioral details such as output format, error conditions, or assumptions about the project object.

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 or redundant statements. It front-loads the core action and resource, and every phrase contributes useful 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?

While annotations and output schema cover some context, the description leaves a major gap around the required project parameter and provides no guidance on workflow placement relative to siblings. For a tool with a nested unconstrained parameter and no schema documentation, this is insufficient for reliable 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 explain the required 'project' parameter at all. Since the parameter is a free-form object with additionalProperties true, an agent cannot determine what fields or structure are expected. The description must compensate for the missing schema information but does not.

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 ('Generate') and clearly identifies the output as a vendor-neutral specification covering compute, memory, storage, network, power, cooling, and security. It distinguishes itself from siblings like generate_bom_tool, which targets a bill of materials, and recommend_architecture_tool. However, it does not explicitly contrast itself with these siblings, so it is clear but not fully differentiated.

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 is provided about when to use this tool versus its siblings such as analyze_inference_project_tool, recommend_architecture_tool, or generate_bom_tool. The context of a pipeline is implied by the sibling list, but the description does not state conditions, exclusions, or sequence.

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