solidworks_exchange

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

Annotations already carry the safety profile (readOnlyHint=false, destructiveHint=true), lowering the bar. The description adds useful context about fallback defaults and unit conventions, but it does not disclose what destructive behavior means here — notably the schema's 'overwrite' field implies possible file overwriting that the description never addresses. No contradiction with annotations.

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?

Three sentences and reasonably compact, but the opening phrase is technical jargon that reduces efficiency. The unit-convention sentence earns its place, while the schema-pointer sentence is somewhat redundant given it points to a schema that provides no descriptions.

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?

This is a high-complexity discriminated union with many per-operation fields, zero schema descriptions, and a destructive annotation. The description is incomplete: it does not explain the export formats, the meaning of options/overwrite, what import_data or arg_string do, or any destructive implications. An output schema exists, which may cover return values, but input semantics are largely missing.

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%, so the description must compensate — but it only explains the dispatch-on-operation mechanism and unit convention, then points to 'the tool's input schema' for field meaning, and that schema has no descriptions. The export format fields (fmt, stl_units, dxf_version, parasolid_version, iges_representation) and import fields (arg_string, import_data) remain entirely unexplained.

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 specific operations ('[export, import]') on a concrete resource (SolidWorks document exchange), which conveys the tool's purpose. However, the phrasing 'dispatches on payload.operation to one of the capability-module handlers' is jargon-heavy, and with 38 siblings the description does not strongly differentiate this from related tools like solidworks_open_document or solidworks_save.

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?

There is no guidance on when to use this tool versus alternatives. None of the sibling tools are named, no conditions or exclusions are given, and no hint of what distinguishes exchange from open/save/import-like siblings. An agent must infer usage entirely from the name.

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