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

Annotations already declare readOnlyHint=true and openWorldHint=false, so "Read-only" is confirmatory rather than additive. What the description does add is the MAPI connection probe — signalling an external application dependency and possible connection failure — plus a preview of the returned inventory including per-key run history. It never says what happens when no model is open or the connection fails, so it is not fully transparent.

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 action and scope are front-loaded in the first clause, and the closing "Call this first" directive is well placed. The middle inventory is a long comma-separated run-on inside one sentence, which is dense but every listed item corresponds to a distinct returned data category.

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?

With no output schema and no parameters, the description carries the full burden of describing return content and does so with a concrete inventory; the connection-health signal is also covered. Missing is any statement about failure/degraded behaviour when CIVIL NX is unavailable or no model is open, which is the one gap an agent would benefit from before calling.

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, so there is nothing for the description to disambiguate; baseline is 4. Mentioning that recent runs are recorded "for this key" hints at implicit keying, but no argument semantics need explaining.

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 pair (checks connection, summarises model) and enumerates exactly what is reported — units, moving load code, row counts, group names, static load cases, stages, combinations, recent runs. That enumeration clearly separates it from nearby siblings such as model_bridge_summary or civil_read_table, so an agent can identify it without opening the schema.

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?

"Call this first" gives explicit ordering guidance relative to the other CIVIL NX tools, which is the main usage decision for a status tool. It does not name a competing sibling or state exclusions (e.g. when to prefer model_bridge_summary), so it stops short of a 5.

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