aedt_start_session

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

No annotations are provided, so the description carries the full burden. It states 'launch or connect,' implying a connection action, but does not disclose behavior such as required permissions, state changes, or potential side effects. The transparency is moderate but incomplete.

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 action. It is concise, but it sacrifices necessary detail. However, this is still within acceptable conciseness for a minimal description.

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 (13 parameters, no annotations, no parameter descriptions), the description is woefully incomplete. It fails to address context like whether the tool starts a new process or connects to an existing one, what the return value is, or how the parameters influence the launch.

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?

With 0% schema description coverage and 13 parameters, the description adds no explanation of parameter meaning or usage. For example, the 'non_graphical' and 'new_desktop' boolean parameters could significantly affect behavior, but the description offers no guidance. This severely undermines correct invocation.

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 'launch or connect' as a verb and 'AEDT application through PyAEDT' as the resource, clearly indicating the tool's action. However, it does not differentiate from sibling tools like aedt_session_info or aedt_release_session, which could lead to ambiguity.

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?

The description provides no guidance on when to use this tool versus alternatives. With over 90 sibling tools, such as aedt_release_session and aedt_session_info, the lack of contextual or exclusionary information makes it difficult for an agent to select the correct tool.

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