solidworks_cam_workflow

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

Annotations already indicate destructiveHint and readOnlyHint; description adds legacy/low-level context and the action list but does not disclose side effects or action-specific behavior beyond that.

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?

Two concise sentences with no redundant content; all information serves to identify purpose and direct the agent to the preferred alternative.

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?

Description is sufficient to avoid misuse by steering toward solidworks_cam and listing the supported raw actions. Output schema exists, so return details are not required, though action-specific invocation details are sparse.

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?

Description lists the raw action values and frames the tool as action/args dispatcher, but does not explain the args object structure, background flag semantics, or per-action parameters. Schema coverage is 0%, so more detail would be needed for full parameter clarity.

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?

Description clearly identifies the tool as a legacy low-level CAM action/args dispatcher for raw CAMService.workflow actions and distinguishes it from the preferred typed solidworks_cam tool.

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?

Explicitly states 'Prefer solidworks_cam' and explains that the typed tool exposes the full CAM operation surface with proper per-operation schemas, giving clear guidance on when not to use this legacy dispatcher.

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