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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds no behavioral details beyond what annotations provide, such as whether the response is static or if there are any side effects. It mentions 'benchmark evidence' and 'beta state,' which are content specifics, not behavioral traits. Since annotations are strong, a 3 is appropriate for the limited added context.

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 description is a single sentence that front-loads the primary purpose ('What this server is and is not') before enumerating additional content. It is concise and avoids unnecessary words, though it could be more structured as a bulleted list. The sentence covers multiple aspects without being verbose.

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, idempotent tool with an output schema (as signaled), the description is sufficient for an agent to know what to expect. It covers the tool's scope, input expectations, and state. The output schema likely details the response structure, so no further return-value explanation is needed 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 has zero parameters, and the schema coverage is 100% (empty schema). The description's mention of 'what to send it' is part of the tool's content, not an indication that this tool takes input. With no parameters to explain, the baseline of 4 is justified; the description adds no parameter information because none is needed.

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 lists the content areas the tool covers (server identity, input expectations, benchmarks, beta state, terms), which makes the purpose reasonably clear. It distinguishes itself from sibling operation tools like match_score or allele_info by being the meta-informational entry point, though it doesn't use a direct 'returns information about the server' phrasing.

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 does not explicitly state when to invoke this tool versus alternatives. It implies it is a reference for understanding the server, but there is no guidance like 'use this first to understand capabilities before making other calls' or 'not for data operations.' The agent is left to infer its role from the content list.

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