freecad_status

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

With no annotations, the description must carry the behavioral burden. 'Verifica' implies a read-only probe, and the three enumerated checks give a decent picture of what it reports, but it says nothing about what happens when FreeCADCmd is not found (error vs. negative result) or whether it touches the filesystem.

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?

A single efficient sentence that front-loads the existence check and then lists version and output folder. No padding, though the trailing clause is slightly less crisp than the opening.

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?

With zero parameters and a declared output schema, the return values need no explanation, and the description names the three data points the agent will get back. The only remaining gap is failure behavior, which is minor for a status probe.

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 takes zero parameters, so the baseline is 4. There is nothing for the description to disambiguate, and it correctly doesn't waste words on inputs.

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 states a specific verb ('Verifica') and three concrete checks: whether FreeCADCmd was found, its version, and the configured output folder. This clearly separates it from action-oriented siblings like freecad_run or freecad_run_file, though it doesn't explicitly distinguish it from freecad_selftest.

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?

Usage is implied by the diagnostic nature of a 'status' check, but the description never states when to call it (e.g., before running a file, to troubleshoot missing FreeCADCmd) nor names an alternative. An agent must infer the pre-flight use case on its own.

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