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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and 'Rein lesend' largely restates that. The description does add that this is the entry point for new notifications, but it says nothing about result ordering, limits, or unread filtering.

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?

The core German description is compact and front-loaded with purpose, then alternatives. The trailing 'EN: end user, customer, portal, notification, map, scope' tag block is keyword padding that does not serve an agent.

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 no-parameter, read-only list tool with full annotation coverage and no output schema, the description covers purpose and routing adequately. Remaining gaps like pagination or whether unread-only filtering is possible are minor.

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?

With zero parameters there is no parameter meaning to explain, so the baseline of 4 applies. The description correctly implies no filtering arguments are needed for the basic list.

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?

'Die eigenen Benachrichtigungen auflisten (Meldungen des angemeldeten Kontos)' gives a specific verb plus resource and explicitly scopes it to the logged-in account. It contrasts itself with ontouser_notification_read and onto_action_logs, so an agent can separate it from its siblings without opening schemas.

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?

It states when to use it ('als Einstieg, um neue Meldungen zu finden') and names the follow-up alternative for marking an item read. It also excludes admin system logs by routing them to onto_action_logs.

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