solidworks_material

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

The description mentions that unspecified fields fall back to defaults and that units follow conventions, but it doesn't disclose side effects or destructive behavior. Given the destructiveHint annotation, describing which operations are destructive would be valuable, but it's absent.

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 brief and to the point, using only two sentences. It avoids redundancy, though its brevity comes at the cost of substantive guidance.

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's complexity—five distinct operations with different required fields, plus a discriminator pattern—the description fails to provide essential context. It doesn't explain what any operation does, when to use them, or how they relate to each other. Highly incomplete.

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 description only notes that each operation has a typed field set and unit conventions. It does not explain any specific parameters like config_name, rgb, entity_name, or density_index. With 0% schema coverage, this is insufficient.

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 tool dispatches on payload.operation to handler modules for five operations, giving a general sense of purpose. However, it doesn't clarify what each operation does or how it differs from sibling tools, so it's only moderately clear.

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 is provided on when to use this tool versus alternatives. It doesn't mention when material operations are needed or how to choose among the listed operations. The description is purely structural, not instructive.

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