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

Annotations already declare a safe read-only, closed-world, non-destructive operation, so the safety profile is covered without description help. The description adds nothing beyond that baseline — no note on whether it returns one or many materials, whether it is deterministic, or what the recommendation is based on.

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?

A single clean, front-loaded sentence with no wasted words. It is efficient, but the brevity is also under-specification rather than disciplined concision.

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 one-parameter recommendation tool with no output schema, the description should at minimum explain what a priority means and roughly what comes back. Neither is present, leaving the agent to guess at both input semantics and return shape.

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 0%, so the description must carry the burden, and it only names the parameter as 'project priority'. The five German enum values (brandschutz, robust, effekt, nachhaltig, feuchtraum) are left entirely unexplained, so an agent cannot tell what each priority means.

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 ('Recommend') and resource ('Caspar material') plus the selecting input ('project priority'). It is distinguishable from list_materials (listing vs. recommending), though it does not explicitly differentiate itself in 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?

No guidance on when to use this versus list_materials or the other siblings, and no prerequisites or exclusions stated. The only implied cue is the word 'Recommend' in the name.

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