undo

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

Annotations already state readOnlyHint=false, idempotentHint=false and destructiveHint=false. The description adds the useful scope detail that only ONE transaction is reverted (no multi-level undo), which is genuine context beyond the annotations, but it says nothing about failure behavior when the undo stack is empty or whether the undo applies per-document.

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 front-loaded sentence with zero filler. It is terse but every word carries meaning; the only shortfall is that brevity here edges toward under-specification rather than being optimally sized for a state-mutating tool.

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 is simple and has an output schema, so return values need not be explained. However, the sole parameter is fully undocumented and the empty-stack / wrong-document cases are unaddressed, leaving gaps an agent would hit in practice.

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 0% for the single doc_name parameter, and the description never mentions it. The agent cannot tell from the definition whether doc_name targets which document's undo stack or what the default empty string implies.

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?

States a specific verb and resource ('Undo the most recent FreeCAD transaction'), so the agent knows exactly what action is performed and that it is limited to the latest transaction. It does not explicitly distinguish itself from the sibling get_undo_redo_status, which keeps it from a 5.

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?

There is no when-to-use guidance, no mention of checking state first via get_undo_redo_status, and no note about what happens when there is nothing to undo. Usage is only inferable from the word 'Undo' itself.

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