get_operation

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not state whether the operation is read-only, what side effects might occur, what input state is required, whether it runs a dry run, or what output shape to expect. This is a critical gap for a tool with such an ambiguous name.

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 very short, but this is under-specification rather than concise effectiveness. It contains no structural information, no front-loaded distinctions, and no useful content that helps an agent decide to invoke the tool.

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 has 9 parameters, no output schema, no annotations, and multiple closely related sibling tools, the description is wholly inadequate. An agent cannot determine the tool's purpose, inputs, outputs, or relationship to alternatives from the provided information.

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%, and the description does not explain any of the 9 parameters. The parameter names like feed, speed, dryRun, toolId, confirmed, outputPath, operationId, and operationIds may hint at meaning, but their roles, relationships, and whether they are filters, settings, or outputs are entirely undocumented.

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 get operation' is essentially a tautology of the tool name 'get_operation'. It states a generic get action on an operation resource but provides no detail on what the operation represents, what is returned, or how this differs from siblings like list_operations or get_operation_parameters.

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 the many alternative operation-related tools such as list_operations, get_operation_parameters, or get_selection. No context, prerequisites, or selection criteria are provided.

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