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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered without the text. The description adds genuine context beyond that: no API key is required, and it enumerates exactly what payload comes back (address, version, online status, players, votes, rank, rating, vote interval, links), which matters because there is no output schema.

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 sentence, front-loaded with the resource and its scope, with the field enumeration and the "no API key" note placed after. The field list is long but earns its place given the absence of an output schema.

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 one-parameter read tool, the definition covers auth requirements and the shape of the returned record, which is the main thing an agent would otherwise lack without an output schema. Minor gaps remain: behavior when the server does not exist, and whether votes/rank fields can be null.

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 description coverage is 100% and the parameter already documents all three accepted identifier forms with examples, so the description can add nothing on that front. Baseline 3 applies: the schema carries the parameter burden entirely.

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?

"One server's public details" plus an explicit field list makes it unambiguous that this is a single-record lookup returning public metadata, distinct from the list/search siblings. It never names those siblings (search_servers, list_my_servers) as the way to obtain the identifier, so differentiation is by inference rather than statement.

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: the singular "one server" framing suggests fetching details once you already have an identifier, contrasting with the plural list/search siblings. There is no explicit when-to-use, when-not-to-use, or routing to search_servers when the id is unknown.

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