create_operation

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only repeats the action 'create'. It does not disclose side effects such as modifying the Mastercam document, whether confirmation or dryRun affects behavior, or what happens to existing operations, toolpaths, or output files.

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 only a three-word fragment rather than a structured, informative sentence. This is under-specification rather than conciseness, and it does not earn its place given the tool's complexity.

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 mutation tool with nine undocumented parameters, no annotations, and no output schema, yet the description offers no context about what creating an operation involves. An agent has no information about required inputs, workflow ordering, side effects, or expected results.

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?

There are nine parameters with 0% schema description coverage, and the description provides no meaning for any of them. Fields like feed, speed, dryRun, confirmed, operationId, operationIds, and outputPath remain completely unexplained, leaving the agent unable to construct a valid call with confidence.

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 'Mastercam create operation' essentially restates the tool name with only the product prefix added. It identifies a create action and an operation resource, but it is a fragment rather than an informative statement and does not explain what an operation means in this context.

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 about when to use this tool versus any alternative. The description does not mention prerequisites, related tools, or situations where another operation-manipulation sibling would be more appropriate, leaving the agent to guess.

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