cst_export_structure_views

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

Since no annotations are provided, the description carries the behavioral disclosure burden. It usefully discloses the connected-mode requirement and names the underlying Plot.ExportImage API, but it does not explain side effects such as file creation, output naming, directory creation, or whether an active project must be open.

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 English first sentence is specific and front-loaded, but the Turkish sentence is a direct duplicate of the same meaning and does not add information. The passage is compact overall, yet the redundant sentence prevents it from being highly polished.

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?

The definition captures the core action, available views, and connected-mode requirement, and the schema provides defaults and the default output directory. Missing pieces include the output file format, behavior when views are omitted, and any project state expectations, so it is adequate but not complete.

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 coverage is 50%, but the remaining parameters are simple and intuitive. The description essentially restates the views list already documented in the schema ('perspective/xy/xz/yz'), adds no meaning for width/height/out_dir, and relies on default values and schema text to carry the rest.

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 uses a specific verb and resource ('Export structure screenshots') and narrows scope to perspective/xy/xz/yz views via Plot. It is clearly distinct from sibling exports like cst_export_cad, cst_export_result, and cst_export_farfield. Even without opening the schema, an agent can tell what this tool does.

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 its use case: use it when structure view screenshots are needed rather than geometry/data files, and it notes the operational prerequisite 'Connected mode required'. However, there is no explicit when-to-use or when-not-to-use guidance and no named alternatives.

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