aedt_optimetrics_summary

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 indicates a read operation by using 'Return', but does not explicitly state that the tool has no side effects, is non-destructive, or requires any permissions. Lack of behavioral details beyond the basic purpose reduces transparency.

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 with no unnecessary words. Every word is functional, and the purpose is front-loaded. It is appropriately sized for a simple retrieval tool.

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 an output schema (not shown) and zero parameters, the description is mostly complete. It does not explain what 'Optimetrics managers' are, but that is domain-specific knowledge. Overall, it is adequate for a list-returning tool with no inputs.

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 tool has zero parameters and schema coverage is 100%. The description adds no parameter information, which is acceptable since there are none. According to guidelines, 0 parameters baseline is 4, and the description does not detract from that.

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 returns 'parametric and optimization setup names from Optimetrics managers', specifying both the verb and the resource. It distinguishes from sibling tools like aedt_create_optimization or aedt_parametric_operation, which create or modify such setups, by focusing on retrieval.

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 usage for querying setup names before acting on them, but it does not explicitly state when to use this tool versus alternatives such as aedt_setup_summary or aedt_create_parametric_sweep. No when-not or alternative guidance is provided.

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