show_body

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

The description reveals no behavioral traits such as whether it affects the model state, requires a specific view setting, or has side effects. With no annotations, the agent has no insight into the tool's behavior beyond the name.

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?

The description is too short, providing minimal information. It is under-specified rather than concise, as it fails to convey essential purpose or usage details.

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 tool's simplicity and the presence of many sibling tools (e.g., 'hide_body', 'get_all_bodies'), the description is completely inadequate. It does not explain what showing a body entails or what the tool returns.

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 coverage is 100% and the parameter 'body_name' has a description 'Body name'. The tool description does not add any additional semantics beyond the schema. Baseline 3 is appropriate.

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 'FreeCAD tool: show_body' is essentially a tautology. It does not specify a verb or clarify what 'show' means (e.g., make visible, highlight, display properties). The sibling 'hide_body' hints at visibility, but the description itself is insufficient.

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 'hide_body' or 'get_all_bodies'. There is no context on prerequisites or typical use cases.

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