get_solution_status

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

There are no annotations, so the description carries the full burden. The leading '[READ ONLY]' text clearly discloses the non-mutating nature of the tool, which is valuable. However, it stops there: it does not state whether the returned status may be stale, require a solve to have been started, or reflect any other behavior such as a server round-trip.

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 one short sentence, with '[READ ONLY]' front-loaded and no filler. It wastes no words and immediately communicates the most important behavioral constraint.

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?

Although the tool has no parameters and an output schema, the description does not help an agent understand what 'solution status' returns or how it fits with siblings such as mechanical_status, get_result_summary, or evaluate_results. The vague 'Inspect Mechanical model data' is too incomplete for an agent to use in a coordinated workflow.

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 has 100% coverage of that (an empty object). The description does not need to explain any parameters, so the baseline of 4 applies; there is no missing parameter-level meaning to compensate for.

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 says 'Inspect Mechanical model data,' which is broad and vague. It never mentions 'solution status' or 'status', so an agent cannot tell this apart from siblings like get_model_summary, get_result_summary, or get_mesh_statistics. The verb–resource pair is present but the actual purpose is not pinned down.

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 given for when to call this tool versus any alternative. It does not name sibling tools, exclude cases, or indicate that it should be used after solve_analysis or solve_analysis. The only signal is the read-only tag, which speaks to safety, not selection timing.

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