Fusion360 MCP Server

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

Annotations indicate this is a mutable, non-idempotent, non-destructive operation, which the description aligns with by implying creation ('Add'). However, the description adds minimal behavioral context beyond annotations—it mentions 'Strategy determines the toolpath type' but doesn't cover error conditions, permissions, or side effects, leaving gaps in transparency.

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 a single, efficient sentence that front-loads the core purpose. It avoids redundancy and wastes no words, though it could be slightly more informative without losing conciseness.

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 (10 parameters, no output schema) and moderate annotation coverage, the description is adequate but incomplete. It covers the basic purpose but lacks details on usage context, behavioral nuances, or output expectations, which are needed for a mutation tool with many parameters.

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?

With 90% schema description coverage, the input schema already documents most parameters well. The description adds some value by explaining that 'Strategy determines the toolpath type', which clarifies the 'strategy' parameter's role, but it doesn't provide additional semantics for other parameters beyond what's in the schema.

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 clearly states the action ('Add a machining operation to a setup') and resource ('machining operation'), distinguishing it from sibling tools like 'cam_create_setup' or 'cam_list_operations'. However, it doesn't explicitly differentiate from other CAM-related tools beyond the strategy mention, which is why it's not a 5.

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?

The description provides no guidance on when to use this tool versus alternatives, such as 'cam_generate_toolpath' or 'cam_post_process', nor does it mention prerequisites like needing an existing setup. It only states what the tool does, not when to apply it.

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