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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description usefully adds domain behaviour: which case types (moving load, settlement, response spectrum, ABS/SRSS anywhere down the combination tree) cannot yield a coexistent state, that the reason and workaround are reported, and that unit conversion is applied. It does not cover cost, size of the payload, or error conditions.

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 scope is front-loaded ('Concurrent Force Reporter, step 1') and there is little filler, but the core is one enormous run-on sentence with semicolon-stuffed enumerations that is hard to parse. The breadth justifies length, yet the structure could be a short bulleted inventory.

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 shape entirely, and it does: the ten LCOM tables, MIDAS addressing, envelope flags, availability reasons, per-result-source items, keyEffect ids with units, groups, stage tokens, criteria/output positions and published status. An agent knows what it will receive 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?

Schema description coverage is 100%, so the schema already documents limit, units, search and includeConstituents. The description restates search and includeConstituents almost verbatim and says nothing about limit caps or the unit-conversion default, so it adds little beyond the schema. Baseline 3 applies.

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: reads the open CIVIL NX model and enumerates everything a concurrent-forces run can consume (load cases, result sources, key effects, groups, stages, units). The 'step 1' framing and 'Read-only' make it separable from concurrent_forces / concurrent_forces_probe, though it never names those siblings explicitly.

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?

Usage context is implied by 'step 1' of a concurrent-forces workflow, and it gives per-parameter advice ('use search to narrow a long case list', 'includeConstituents shows each combination's children'). But there is no explicit statement of when to call this versus concurrent_forces_probe or concurrent_forces, nor any prerequisite/exclusion guidance.

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