aedt_api_manifest

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

No annotations are provided, so the description must disclose behavioral traits. It notes that the tool works 'without launching AEDT', indicating it is non-disruptive and lightweight. However, it does not mention permissions, side effects, or what happens when parameters are omitted, leaving some gaps.

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 sentence that immediately conveys the core action and resource. It is concise and front-loaded with the most important information, containing no superfluous words.

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 two optional parameters, no required parameters, and an output schema, the description adequately states the purpose and a key behavioral trait (no AEDT launch). However, it lacks parameter guidance, which is needed for a complete understanding of how to use the tool effectively.

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?

The input schema has 0% description coverage, meaning no parameter is described in the schema. The tool description also fails to explain the purpose or behavior of the parameters 'app_name' and 'include_private'. Without any guidance on how these affect the output, the description adds no value over the raw schema.

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 lists PyAEDT app constructors and method signatures, which is a specific verb and resource. It distinguishes itself from sibling tools like aedt_analyze or aedt_create_geometry by focusing on listing API elements without launching AEDT.

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 implies the tool is for exploring API without launching AEDT, but it does not explicitly provide when to use or not use this tool versus siblings like aedt_list_api or aedt_session_info. No exclusions or alternatives are mentioned.

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