execute_macro

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

With no annotations, the description must disclose behavioral traits. It provides none, leaving the agent uninformed about side effects, required permissions, or whether execution modifies the 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?

Extremely concise but at the cost of informativeness. A single phrase 'FreeCAD tool: execute_macro' is under-specification, not efficient communication.

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 complexity of a macro execution tool with a flexible parameter (anyOf array/string), the description is completely insufficient. There is no output schema, and the description fails to explain the tool's function or return behavior.

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?

Though schema description coverage is 100% with the parameter 'commands' having a description, the tool description adds no extra meaning. It does not explain what 'tool_name, arguments' entails or how the macro executes, so value beyond schema is minimal.

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?

Description is 'FreeCAD tool: execute_macro' which merely restates the name without specifying what the tool does or what a macro execution entails. It fails to distinguish from sibling tools that also operate on FreeCAD models.

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?

No guidance is provided on when to use this tool versus alternatives like 'undo' or 'extrude_sketch'. No context for appropriate usage scenarios.

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