aedt_export_app_data

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

No annotations are provided, so the description must carry the full burden. It only mentions 'Export through PyAEDT export methods', which is vague. It does not disclose side effects (e.g., file writes), authentication needs, or what the output schema contains. For a mutation-like export operation, this is insufficient.

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 concise sentence, but it sacrifices necessary detail. It is front-loaded with the action, but the brevity results in insufficient information for correct invocation.

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 having an output schema (not provided), the description lacks critical context: what the tool returns, side effects, parameter semantics. For a tool with 3 parameters and low schema coverage, more detail is needed. The description leaves major gaps.

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%, meaning the schema provides no parameter descriptions. The description does not explain the parameters either. It does not describe the meaning of different export_kind enum values or how to use args and kwargs. The agent has no guidance on parameter usage.

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?

Description says 'Export common AEDT design artifacts through PyAEDT export methods.', which is clear about the action (export) and resource (AEDT design artifacts) but vague and does not distinguish from sibling export tools like aedt_export_diagnostics or aedt_export_report. The enum values in the schema provide specificity, but the description itself lacks it.

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. Sibling tools include many export functions with specific names, but the description does not explain when to choose this general export over them. No when-not-to-use or prerequisite information.

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