aedt_create_parametric_sweep

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

With no annotations, the description carries full burden but fails to disclose any behavioral traits. It does not mention side effects, required permissions, return behavior, or any constraints beyond creation. The tool mutates design state, but this is not clarified.

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 very concise (8 words) but under-specifies the tool's behavior. While brevity is positive, it sacrifices necessary detail. The structure is a single sentence without any contextual framing.

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 the tool has 6 parameters and an output schema, the description is incomplete. It does not explain the purpose of optional parameters, the expected input formats, or the nature of the output. Without additional context, an agent cannot correctly invoke this tool without schema inspection.

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%, yet the description adds no parameter-level information. It does not explain what 'variable', 'start', 'stop', 'step' represent, nor the optional 'name' or 'variation_type'. The schema titles are minimal and the description offers no compensation.

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 clearly states the tool creates a parametric sweep, specifying the resource (Optimetrics parametric sweep) and action (create). It distinguishes from siblings like aedt_create_frequency_sweep by the term 'parametric sweep', but could be more explicit about the variable range.

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 usage guidelines are provided. The description does not indicate when to use this tool over alternatives like aedt_create_frequency_sweep or aedt_create_optimization, nor does it mention any prerequisites or exclusions.

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