Fusion360 MCP Server

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

Annotations indicate this is a non-read-only, non-idempotent, non-destructive operation, but the description adds value by clarifying it's a transformation step (toolpaths to G-code). However, it doesn't disclose key behavioral traits like whether it overwrites files, requires specific permissions, or has rate limits. With annotations covering basic safety, the description provides some context but lacks depth on operational behavior.

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 with zero waste. Every word earns its place by clearly stating the tool's function and output, making it easy for an agent to parse quickly.

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 (transforming toolpaths to machine code) and lack of output schema, the description is minimally adequate. It states what the tool does but doesn't cover output details (e.g., file format, error handling) or integration with siblings. With annotations providing basic hints and schema covering most parameters, it's functional but leaves gaps for a tool in a CAM context.

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 80%, so the schema already documents most parameters well. The description doesn't add meaning beyond the schema—it doesn't explain parameter interactions (e.g., how 'operation_name' affects output) or provide examples. This meets the baseline for high schema coverage but doesn't compensate for the 20% gap or enhance understanding.

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 tool's purpose: 'Post-process toolpaths to generate NC code (G-code)'. It specifies the verb ('post-process') and resource ('toolpaths'), and the output ('NC code/G-code'). However, it doesn't explicitly differentiate from sibling tools like 'cam_generate_toolpath' or 'execute_code', which might handle related but different steps in the CAM workflow.

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. It doesn't mention prerequisites (e.g., needing a generated toolpath first), exclusions, or how it fits into the workflow with siblings like 'cam_generate_toolpath' or 'execute_code'. This leaves the agent to infer usage from context alone.

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