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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false) by disclosing that the login is shared by all readers, that feedback is not private, that the operator reads it, and that it may be published as a public example — with an explicit instruction not to include personal data. This is exactly the kind of consequence-level disclosure annotations cannot carry.

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?

Purpose and the privacy warning are front-loaded, and the auth details follow in logical order. The appended English parenthetical partially duplicates the German text, costing some tightness but aiding clarity for non-German agents.

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?

An output schema exists so return values need not be described, and the auth flow plus the privacy consequence are covered. The only real gap is the unexplained `page` parameter and any indication of what happens after submission (e.g., whether a confirmation or link is returned).

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 0%, so the description must compensate. It explains `token` well (source: login window connection, `login` tool, or demo credentials) and implicitly characterizes `message` as free text with a privacy caveat, but the `page` parameter is never mentioned, leaving one of three params undocumented.

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 (send) and resource (feedback) plus the recipient (the operator of was-ist-mcp.ch), which no sibling tool covers. An agent can distinguish it from `login` or `get_page` at a glance.

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?

Explains the prerequisite clearly: a login is required, and the token can come either from a connection initiated in the login window or from the `login` tool, or from the demo page credentials. It names the sibling that supplies the token, though it does not state explicit when-not-to-use conditions.

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