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 minimal behavioral context beyond 'disable'. It doesn't clarify what 'suppress' entails (e.g., temporary vs. permanent, visibility changes, or impact on dependencies), nor does it mention permissions, side effects, or error conditions. No contradiction with annotations exists.

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 action and resource without unnecessary words. It earns its place by conveying the essential purpose clearly, making it highly concise and well-structured.

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 (a mutation operation with no output schema and low schema coverage), the description is inadequate. It lacks details on behavior, parameter usage, return values, or error handling, leaving significant gaps for an AI agent to understand how to invoke it correctly in 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?

With 0% schema description coverage and one parameter ('feature_name'), the description provides no additional meaning about the parameter. It doesn't explain what constitutes a valid feature name, format expectations, or examples, leaving the schema to carry the full burden without compensation from the description.

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 ('suppress/disable') and resource ('a feature in the timeline'), making the purpose immediately understandable. It distinguishes from sibling 'unsuppress_feature' by specifying the opposite action, though it doesn't explicitly differentiate from other tools that might modify features.

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 like 'unsuppress_feature' or other modification tools. It lacks context about prerequisites, such as whether the feature must exist or be active, and doesn't mention any exclusions or typical scenarios for its application.

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