FreeCAD MCP Server

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

No annotations are provided, so the description carries full burden. It clearly describes the behavior: reloads all handler modules and re-registers them with the RPC server. However, it doesn't mention potential side effects like temporary service interruption or error handling if modules fail to reload.

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?

Perfectly concise with three focused sentences. First sentence states the action, second provides usage context, third explains the implementation details. Every sentence adds value with zero waste.

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?

For a 0-parameter tool with no annotations and no output schema, the description provides good context about what the tool does and when to use it. However, it doesn't describe what happens on success/failure or what (if anything) is returned, leaving some behavioral gaps.

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?

The tool has 0 parameters with 100% schema coverage, so the baseline is 4. The description appropriately explains that no parameters are needed for this operation, which aligns with the empty input 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 specific action ('hot-reload all FreeCAD addon handler modules') and resource ('handler modules in freecad_addon/handlers/'). It distinguishes from siblings by focusing on code reloading rather than analysis, execution, or inspection operations.

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?

Explicitly states when to use this tool ('after editing handler code') and provides clear context about its purpose (picking up changes without restarting FreeCAD). No alternative tools are mentioned since this is a unique reload operation among the siblings.

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