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

With no annotations provided, the description carries the full burden. It discloses that the tool returns observed data, includes a catalog-wide drift rate for baseline comparison, and implies a read-only observation operation. It does not explicitly state that it performs no mutation or that it may fail for unknown server names, but the read-only nature is strongly implied by the content described.

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 two sentences, front-loads the core purpose, and packs the response contents into a compact list. Every clause adds information: endpoint reachability, timestamps, repository activity, hash, change count, and the drift-rate baseline. No filler or repetition.

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 single-parameter read tool with no output schema, the description covers the key return fields and even adds the drift-rate baseline context. It lacks an explicit statement of what happens when the server name is not found or whether the tool requires prior registration, but the overall picture is sufficient for an agent to decide to call it.

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 0%, so the description must compensate. It explains what the tool returns but does not elaborate on the 'name' parameter beyond the schema's title 'Name' — for example, whether it is a display name, a slug, or a server ID. The description's focus on the response means the single parameter's semantics are only minimally clarified.

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 names a specific verb ('get') and resource ('one MCP server') and enumerates the exact data returned: endpoint reachability, last-checked/last-verified timestamps, repository activity, tool-definition hash, and 90-day change count. It also distinguishes itself from siblings by focusing on a single server's observed state rather than changes, tools, or search.

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 clearly implies this is for retrieving a consolidated status snapshot of one server, and the sibling list (get_server_changes, get_server_tools, get_spec_status, search_servers, watch_server) provides implicit alternatives. However, it does not explicitly state when to choose this over those siblings, such as 'use get_server_changes for a detailed change log' or 'use search_servers when you don't know the exact name.'

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