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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, consistent with a pure calculator, so the bar is lower. The description goes beyond them by enumerating the returned result quantities and disclosing the 2/3 safety factor applied to Zs,max, which is real added context an agent could not infer otherwise.

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?

Two sentences: the first front-loads purpose and normative basis, the second enumerates outputs with units. No filler, though the output enumeration is slightly list-like rather than integrated prose.

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?

No output schema exists, so the description correctly compensates by listing the four return values with units, and the input schema fully covers the five parameters. It would be stronger if it stated the computation is side-effect-free and deterministic rather than leaving that to annotations.

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%, with titles, ranges, defaults and even the LS-type-to-factor mapping documented inline. The description adds nothing about m, u0, i_n, z_s or region, so baseline 3 is appropriate since the schema already carries the full burden.

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 ('Berechnen') and concrete resources (Abschaltstrom, zulässige Schleifenimpedanz, Kurzschlussstrom, Reserve) scoped to DIN VDE 0100-410/600. The purpose is unambiguous, though the opaque tool name 'bot_038' and the undifferentiated sibling list mean no differentiation can be signalled beyond the title.

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?

The standards reference (DIN VDE 0100-410/600) implies the engineering context in which the tool applies, and 'erforderlichen Abschaltstrom' implies a verification/design scenario. However there is no explicit when-to-use, no when-not-to-use, and no alternative tool named — usage must be inferred.

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