get_faces_info

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

The description discloses no behavioral traits such as read-only nature, required permissions, side effects, or response format. With no annotations provided, the agent has zero insight into tool safety or performance.

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 extremely short but fails to be concise because it does not convey any meaningful information beyond the tool name. It does not earn its place; a useful description would explain the tool's function.

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 complexity (it returns face information for 3D models) and the lack of an output schema, the description is grossly incomplete. The agent cannot infer what data is returned or how to interpret results, especially compared to sibling tools with richer descriptions.

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 input schema has 100% description coverage for the single parameter 'body_name', which is adequately described in the schema itself. However, the tool description adds no additional context about parameter usage, defaults, or constraints beyond what the schema provides.

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: get_faces_info' is a tautology that merely restates the tool name without specifying what information about faces is retrieved or how it can be used. It fails to distinguish from sibling tools like get_edges_info or get_body_dimensions.

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 such as get_edges_info or select_face. The description does not mention prerequisites, selection methods, 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.