FreeCAD status

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

No annotations are provided, so the description carries the full burden. It does add real value: it declares the call non-mutating and safe at any time, discloses the failure path (available=false plus guidance), and sketches the success payload. It doesn't mention cost, latency, or whether repeated calls re-probe the installation, but for a trivial read-only check the disclosure is adequate rather than rich.

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?

Three short sentences, front-loaded with the core purpose, then the return shape, then the failure mode and safety note. Every sentence adds distinct information with no repetition of the title.

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?

The tool takes no parameters, is a simple read-only probe, and has an output schema for the returned fields. The description covers the one thing the schema cannot: what happens when FreeCAD is absent, and that calling it is always safe.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a no-argument invocation.

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?

Uses a specific verb ('Report') against a specific resource (a usable FreeCAD installation) and enumerates what is returned: version, embedded Python version, Part workbench availability. It implicitly separates itself from sibling tools like server_info and the create_* tools by being purely a reachability check, though it never names that sibling to sharpen the distinction.

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?

'Safe to call at any time' clearly signals it is a non-destructive preflight/health check, and 'Returns available=false with guidance when FreeCAD is missing or fails to start' tells the agent what to expect on failure. It stops short of explicitly routing the agent here before calling create_document or other FreeCAD-dependent siblings.

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