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

readOnlyHint=true already declares the safe-read profile, so the description's burden is lighter. It does add genuinely non-structured facts — the read covers both received and offered licenses, includes status, is limited to the current workspace, and is 'Free' (no credit cost). It stops short of describing result shape, ordering or pagination.

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 short sentences with the scope and coverage front-loaded and no filler. The trailing 'Free.' fragment is efficient but slightly opaque out of context (cost vs. license-type ambiguity).

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 parameterless, read-only listing with no output schema, the description covers what is listed, in what state, and in what scope — enough to call it correctly. Only the shape of the returned list (fields, ordering) is left unstated, which is a minor gap here.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The stated scope ('current workspace') usefully explains why no workspace argument exists.

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 ('List') and resource ('received and offered asset licenses') plus scope ('current workspace'), which separates it from the mutation siblings like lab_lizenz_anbieten or lab_lizenz_annehmen. It never names a sibling explicitly, but the list-vs-act distinction is inferable.

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 only implied — an agent deduces it calls this to see the license state before acting. There is no explicit when-to-use, no precondition (e.g. required workspace context), and no pointer to an alternative such as lab_list_assets for the underlying assets.

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