aedt_modeler_operation

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

No annotations are present, so the description bears full responsibility. It mentions 'allowlisted' but does not define it or disclose behavioral traits like side effects, permissions, or error conditions. The description gives only high-level categories without operational specifics.

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 short (one sentence) and front-loaded, which is good for conciseness. However, it lacks necessary details, making it insufficient for an agent to use the tool correctly. The structure is minimal but not wasteful.

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 3 parameters, no annotations, and an output schema that is not described, the description is too sparse. It provides a high-level purpose but fails to guide the agent on how to invoke the tool or interpret its output.

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 adds no information about any parameter. The method, args, and kwargs are left entirely unexplained, giving the agent no help on valid values or expected formats.

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 runs modeler operations for categories like transforms, booleans, sweeps, groups, or regions. It provides a specific verb and resource, but does not differentiate it from sibling tools like aedt_circuit_operation or aedt_configuration_operation, which slightly reduces clarity.

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?

There is no guidance on when to use this tool versus alternatives. The description lists operation categories but does not explain when a modeler operation is appropriate over other operations or provide any contextual cues.

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