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

Annotations already declare readOnlyHint and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: it mirrors the RC Slab & Shell Assessment plugin's behavior, derives orientation groups from plate normals with a suggested in-plane reference, and reports each case with the sign/sense it must be requested by — non-obvious semantics an agent could not infer.

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?

Front-loaded with the verb and resource, then a compact second sentence on sequencing. The parentheticals (ELEM/NODE, all LCOM tables) add precision, though the first sentence is long and dense enough to cost a point.

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 a single filter parameter, the description does the heavy lifting by describing what is returned (plates, groups, cases, combinations, orientation groupings, sign senses). An agent has enough to call it correctly and interpret the result; only explicit return structure is left implicit.

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?

Only one optional parameter and schema coverage is 100%, so the schema already documents the group filter and its default ('every plate'). The description adds no further semantics about group naming or scoping beyond 'the open model's plates', so the 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 (reads) and enumerates the exact resources: plates (ELEM/NODE), structure groups, static cases and combinations (LCOM tables), plus derived orientation groups by plate normal. It also positions itself against the sibling slab_assess, so an agent can distinguish it without opening either 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?

"Read-only; use it before slab_assess" gives an explicit ordering and context for invocation. It stops short of naming when-not to use it or alternatives such as model_bridge_summary for non-slab surveys, so it is clear but not fully routing.

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