calculate_mass_properties

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

No annotations are provided, so the description bears full responsibility. It claims to 'calculate and return' mass properties but does not disclose whether the tool modifies the model, requires an active document, or any error conditions. The read-only nature is implied but not explicit.

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 concise with two sentences, front-loaded with the main purpose. It efficiently states what the tool does and why it's useful, though it could be more precise about inputs and the specific output schema.

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 that the tool has a nested input parameter and an output schema, the description provides a reasonable overview of outputs. However, it lacks details on the 'current model' requirement, the input structure, and differentiation from the sibling 'get_mass_properties'.

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% documentation coverage on all properties, so the baseline is 3. The description adds no additional meaning to the parameters; it merely lists output properties. No parameter names or semantics are elaborated beyond the schema.

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 clearly states 'Get mass properties of the current SolidWorks model' and lists the specific properties computed (volume, surface area, mass, center of mass, moments of inertia). However, it does not differentiate from the sibling tool 'get_mass_properties' which has a very similar purpose.

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?

The description mentions it is 'essential for engineering analysis, weight calculations, and structural design,' providing some context. However, it lacks explicit guidance on when to use this tool versus alternatives, such as the similarly named sibling 'get_mass_properties', and does not state any prerequisites or conditions.

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