aedt_batch_call

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

With no annotations, the description carries full burden but only mentions 'ordered' calls. It does not disclose whether the tool is destructive, error handling behavior (despite having continue_on_error param), auth needs, or side effects. Minimal behavioral context.

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, efficient sentence that front-loads the core purpose. There is no fluff or unnecessary repetition. Every word contributes value.

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's complexity (batch execution, two parameters) and lack of nested schema descriptions, the description is too minimal. It does not clarify how to format operations, the execution order guarantee, or error propagation. Output schema exists but does not compensate for missing parameter 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 coverage is 0% and the description adds no parameter details. It hints that operations contain calls but does not explain the structure of each operation object, the meaning of continue_on_error, or required fields. The agent gets little help from the description.

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's function: executing ordered public PyAEDT/native AEDT calls in one MCP request. It uses specific verbs and resources, and distinguishes from sibling tools like aedt_call by indicating batching.

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 on when to use this tool vs alternatives (e.g., aedt_call for single calls or aedt_solve_in_batch). The description does not mention prerequisites, when it should be prioritized, or when to avoid it.

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