get_mesh_statistics

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

No annotations are provided, so the description carries the behavioral burden. It does explicitly disclose '[READ ONLY]' and uses the non-mutating verb 'Inspect', which is useful. However, it does not mention prerequisites, limitations, or what happens if no model is active, leaving behavioral context relatively thin.

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 a single sentence with 'READ ONLY' front-loaded, making it concise and scannable. Every word earns its place, though the content is slightly generic and under-specified for a tool in a large sibling family.

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 has no parameters and an output schema exists, so return-value details are covered and do not need to be explained. However, the description does not say that this returns mesh-specific statistics or when to choose it over get_model_summary or get_geometry_bodies, which is a noticeable gap given the many sibling tools.

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 tool takes zero parameters and the schema is empty with 100% coverage, so the baseline for a no-parameter tool is 4. The description adds no parameter detail, but none is needed because there is nothing to document.

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 gives a clear verb and resource ('Inspect Mechanical model data') and explicitly labels the operation READ ONLY, but it does not mention 'mesh statistics' or differentiate itself from similar inspection siblings like get_model_summary and get_geometry_bodies. It is not a tautology, but it is too generic to be a precise purpose statement.

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 guidance on when to use this tool versus alternatives. The description does not say that this tool is for mesh-specific statistics, name any sibling for comparison, or mention prerequisites such as an active Mechanical model or connection. An agent must infer usage entirely from the tool name.

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