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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real context beyond them: it returns bundled theory content and explicitly NOT interpretation of a specific simulation run, which prevents a common misinvocation. It stops short of describing the returned content's shape or size, which matters somewhat since there is no output schema.

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 core definition, then scope, then usage triggers, then the exclusion — a well-ordered structure. It is dense but nearly every clause earns its place; the concept enumeration is somewhat redundant with the schema enum.

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?

For a single-parameter, read-only lookup tool with no output schema, the description covers purpose, scope, invocation triggers, and the nature of the return value. There is nothing an agent needs in order to call this correctly that is missing.

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 coverage is 100% and the single enum parameter is already documented in-schema, so the baseline is 3. The description's concept list loosely maps human-readable names ('Gain/Loss methodology', 'Buffer Tradeoff') onto the enum slugs (gain_loss, buffer_tradeoff), adding slight value, but it introduces no new semantics about the parameter itself.

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?

Names a specific resource (definitional primers for named ReliaSim framework concepts) and enumerates them — Constraint, Buffer, Interrupt, Converter, cascading losses, OEE, Gain/Loss, Buffer Tradeoff. It explicitly contrasts itself with the sim tools, so an agent can distinguish it from run_gain_loss / run_buffer_tradeoff 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?

Gives explicit when-to-use triggers ('what is X?', 'how does X work?', 'explain the framework') and an explicit when-not with the alternative named: for line-specific claims (throughput, availability, what-if) call the sim tools instead. Nothing about routing is left to inference.

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