aedt_cleanup_solution

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only says 'clean solution data', not clarifying whether data is permanently deleted, if it affects other data, or if the operation is reversible. This is insufficient for a mutation tool.

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, which is concise, but it lacks the necessary depth to be useful. It is front-loaded but too brief, leaving out critical context.

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 5 parameters, no explanations, and the presence of an output schema (not elaborated), the description is incomplete. The agent cannot reliably invoke this tool with correct parameters or understand the cleanup scope.

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 5 parameters with 0% description coverage, and the tool description adds no explanation of their meaning or usage. The parameters like 'entire_solution', 'field', 'mesh', 'linked_data' are left entirely to the agent to infer from names. This is a major gap.

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 states the verb 'Clean' and resource 'solution data', and references PyAEDT cleanup_solution options. It distinguishes itself from sibling tools like aedt_analyze or aedt_create_frequency_sweep by specifying cleanup, but 'solution data' is somewhat vague.

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 like aedt_analyze or aedt_delete_item. No context for prerequisites or typical usage scenarios is given.

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