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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds genuine value by disclosing the payload shape (metadata, status, p50/p95 latency, checks, tool list, measured timestamps, server page URL), which matters because no output schema exists; it stops short of stating error behavior or freshness guarantees.

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 dense sentence that front-loads the verb and resource, then lists return contents. Every clause carries information; the trailing "with measured timestamps and the server page URL" is slightly tacked-on but still informative.

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 with no output schema, the description covers the essentials: what it fetches and what comes back. Missing only edge-case behavior (unknown id, data staleness), which is a minor gap given the annotations already establish it as a safe idempotent read.

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?

Only one parameter exists and the schema documents it fully at 100% coverage, including a pattern and a concrete example id. The description adds no further meaning about the id beyond what the schema already says, so the baseline of 3 applies.

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?

Specific verb "Return" plus a precise resource (one server) and an enumeration of what that record contains: metadata, status, latency p50/p95, checks, and tool list. It is clearly distinguishable from siblings like list_categories or find_tools, but it never names an alternative, so differentiation is inferred rather than stated.

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 implied: use this when you already have a specific server id and want its full detail. There is no explicit when-to-use guidance, no mention of when to prefer search_servers or check_status instead, and no note about what happens if the id does not exist.

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