aedt_native_module_batch_call

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

With no annotations provided, the description must disclose behavioral traits. It mentions 'ordered calls' implying sequential execution, but does not discuss idempotency, side effects, error handling, or the effect of the continue_on_error parameter.

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), which is concise but sacrifices information. It front-loads the core action but could be expanded with key details without becoming verbose.

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 the presence of an output schema, the description fails to explain critical aspects: what constitutes a valid 'call', how 'module_name' maps to AEDT modules, and the behavior of 'continue_on_error'. The tool is complex enough to require substantially more context.

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 tool description adds no explanation of the three parameters (module_name, calls, continue_on_error). The meaning of 'calls' array and its expected structure are left undefined.

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 specifies the verb 'run' and the resource 'ordered calls against one AEDT native module', and references the method to obtain the module (odesign.GetModule). This distinguishes it from sibling tools like aedt_batch_call and aedt_native_module_call, but does not elaborate on what 'ordered calls' entails.

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 use this tool versus alternatives such as aedt_native_module_call or aedt_batch_call. The description does not specify prerequisites, limitations, or recommended scenarios.

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