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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the result is the 'full' listing and that behavior is identical to get_server, which is genuine value. It does not say what happens when a slug is invalid or how large the listing is, which are the remaining behavioral gaps.

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?

Two short sentences, front-loaded with the primary action and followed by the disambiguating alias note. No filler or redundant restatement of the title.

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?

With one required parameter, no output schema, and full annotation coverage, this description covers nearly everything an agent needs to select and invoke the tool. The only omission is failure behavior for unknown slugs. Return contents need not be spelled out since there is no output schema to rely on, though a hint about what the listing contains would help.

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 single parameter has 0% schema description coverage, so the description must carry the load. It does add meaning by tying the slug to search_tools output, which tells the agent where to obtain a valid value. It does not describe slug format or whether slugs are case-sensitive, so the compensation is partial rather than complete.

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 and resource: retrieves 'the full MCP Harbor listing for one tool', keyed by slug. It also identifies itself as an alias of get_server, which pre-empts confusion with that sibling. The only weakness is that 'MCP Harbor listing' is somewhat jargon-y about what is actually returned, but the retrieval intent is unambiguous.

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 parenthetical '(as returned by search_tools)' tells the agent where the slug comes from and implies the search_tools -> get_tool workflow. Because the tool is an alias of get_server, no further sibling differentiation is needed. It stops short of stating when NOT to use it (e.g., batch retrieval or fetching by server rather than tool).

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