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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value by disclosing the payload contents (criteria, letter scale, evidence burden, independent review, dispute procedure), which is meaningful since there is no output schema. It does not cover other behavioral traits such as caching, auth, or versioning.

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 front-loaded sentence naming the resource and then listing its components after a colon. No wasted words, no preamble, appropriately sized for a no-required-parameter read tool.

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 fills the gap by enumerating the returned content, and the read-only annotations remove the need for behavioral warnings. Only the absence of any usage/routing guidance keeps it from being fully complete.

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?

There is a single parameter (markt) with 100% schema description coverage, including the enum values and the note about UK pricing in pounds. The description says nothing about this parameter, so baseline 3 applies — the schema carries the semantics.

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 resource ('het volledige SupplementScore-scoremodel') and enumerates its components (criteria, letterschaal, bewijslast, review, dispuutprocedure), so an agent can immediately tell this returns the scoring methodology rather than a product or price. It is clearly distinct from every sibling, none of which covers the model itself. It lacks an explicit verb like 'get/retrieve', but the intent is unambiguous.

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?

There is no statement of when to call this versus alternatives, no prerequisites, and no exclusions. Usage is only inferable from the fact that it returns the scoring model, but nothing in the text guides the agent on timing or routing.

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