check_mesh

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that it returns stats, failures and advice, but says nothing about the execution side effects (a run writes/overwrites log.checkMesh), the wait_seconds timeout behavior, or what happens when no log exists and run=false.

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?

A single front-loaded sentence with no filler, stating action first and return content second. It is efficient, though arguably terse given the tool's four parameters and absent 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?

There is no output schema, so the description must carry the return contract; it does name the three categories of returned data, which is the minimum. It omits anything about timeout/failure behavior, the log-parsing fallback path, or argument pass-through semantics, leaving meaningful gaps for a 4-parameter tool.

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 description coverage is 75%, and the schema itself explains `run` and `args` well; only `wait_seconds` lacks a description. The description contributes no parameter-level meaning beyond the schema, so the baseline 3 for high coverage with a thin description 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?

States a specific verb and resource (run checkMesh, an OpenFOAM mesh quality utility) and names the return payload: structured mesh statistics, failed checks, practical advice. It does not, however, distinguish itself from sibling tools like `run` or `read_log`, which an agent could plausibly pick for a similar job.

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 when-to-use guidance at all: nothing says whether to reach for check_mesh versus the generic `run` tool, nor when to invoke it (e.g., before running a solver). The only usage hint lives in the schema (`run=false` parses an existing log), which is structured data rather than description guidance.

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