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

Annotations already establish that this is a read-only, idempotent, closed-world operation; the description adds the concrete behavioral output (three named quantities with units), which is real information beyond the annotations. It does not mention numerical precision or rounding, which is the only notable gap for a computation tool.

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?

It is short and front-loaded, with the operative computation first and the return values last. Minor waste: 'Einfach und kostenlos' is marketing filler, and the three output quantities are effectively listed twice, though the second listing adds the units.

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, the description correctly compensates by spelling out the three returned values and their units, and the input side is fully covered by a 100%-documented schema. The only missing piece is what the region parameter changes in the result, which is left unstated.

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 types, defaults, ranges, and the region enum all documented, so the schema carries the parameter burden and the baseline of 3 applies. The description confirms the input geometry ('aus Tiefe und Neigungswinkel') but adds nothing about the region parameter's role in the calculation.

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?

The description names a specific verb and resource ('Dachneigung für ein Pultdach berechnen') and enumerates exactly what is computed and from which inputs, so an agent immediately knows what the tool does. It cannot differentiate the tool from its siblings, but all siblings are opaque bot_0XX identifiers, so that differentiation is not achievable through this text.

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 is implied: an agent can infer it should call this when it needs the pitch, rise, or rafter length of a mono-pitch roof. There is no explicit 'use this instead of X' routing and no statement of prerequisites or exclusions, though for a self-contained calculator there may be no meaningful alternatives.

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