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

No annotations are provided, so the description carries the full burden. It discloses the grouping behavior, the output (Titel und URL), and the optional filter. It implies a read-only operation via 'Listet', but does not explicitly state that it has no side effects, nor does it mention any pagination, limits, or output volume beyond the token-saving hint. Adequate but not rich.

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, front-loaded with the core purpose and output, followed by the optional usage tip. No filler or redundant phrasing. Every sentence earns its place, and the structure is efficient for an agent to parse quickly.

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 simple listing tool with no output schema and no annotations, the description covers the essential information: what it returns (Titel und URL), how results are organized (by cluster), and the optional filter. Minor gaps exist (e.g., behavior on invalid cluster, whether results are paginated), but they are not critical for a straightforward overview tool. The token-saving hint implicitly warns about potentially large output.

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 coverage is 100%, so baseline is 3. The description adds value beyond the schema by explaining the rationale for using the optional cluster filter ('um Tokens zu sparen') and reinforces the meaning ('nur ein Thema listen'), which is not present in the schema description. This adds practical guidance on when and why to pass the parameter.

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 states a specific verb ('Listet'), a resource ('alle verfügbaren Lernmodule'), a scope ('alle', grouped by cluster), and the return fields (Titel und URL). This clearly differentiates from the sibling search tool (lernmodule_suchen) which implies targeted retrieval rather than a full listing. No ambiguity.

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 description gives a clear usage hint for the optional parameter ('um Tokens zu sparen'), but it does not explicitly state when to use this overview tool versus the search or read tools. The context is implied (listing vs. searching vs. reading), but no direct alternative routing is provided.

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