aedt_export_matrix_data

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

No annotations provided, so description must cover behavioral traits. Only states 'Export' but lacks details on side effects, required project type, file output format, or if it overwrites existing data.

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?

One sentence, no wasted words, but severely under-specified for a tool with three parameters. Conciseness is not helpful when it omits critical information.

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 complexity of matrix export with enum types and optional arguments, the description is insufficient. Output schema exists but description does not mention return behavior or required project context (e.g., Maxwell vs Q3D). Sibling tools suggest variety, yet no usage context provided.

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 description provides no explanation of the three parameters (export_kind, args, kwargs). The enum for export_kind is listed in the schema but not described in the text, leaving the agent without usage semantics.

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 clearly states verb 'Export' and identifies resource as 'Maxwell/Q3D matrices or Q3D equivalent circuits', distinguishing it from sibling export tools like aedt_export_field_plot or aedt_export_report. However, no explicit differentiation from other export tools in the sibling list.

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. Among many sibling export tools, there is no contextual advice on selection criteria or prerequisites.

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