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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions that it follows the same safety rules as the website and selects the first safe endpoint, which is useful. But it does not disclose what happens if no safe endpoint exists, error behavior, or whether the operation has side effects (it appears read-only, but that is not stated explicitly).

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 sentences, both purposeful and front-loaded. The first sentence states the core action and scope; the second adds a precise reference to the mirrored behavior, ensuring the agent knows exact fidelity. No redundant words or vague filler.

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 tool with only 2 required parameters and no output schema, the description adequately explains what the tool does and what it produces. It does not describe potential failure modes (e.g., server not found) but given the simplicity and that the schema fully documents inputs, this is a minor gap. The description is sufficient for an agent to invoke it correctly.

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%: both 'slug' and 'client' are described with examples and enum values. The description adds little beyond what the schema already provides, only reinforcing that the client parameter dictates the format. This meets the baseline of 3 but does not exceed it.

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 states a specific verb ('Generate') and a precise resource ('ready-to-paste install snippet for one server's first safe remote endpoint or installable package'), and clarifies the output format is client-specific. It clearly distinguishes this tool from siblings like get_server or search_servers, which handle discovery rather than config generation.

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?

It provides clear context: it is for generating a snippet for a single server's first safe endpoint, and explicitly mirrors the Connect block on mcpnav.dev. However, it does not name alternative tools or state when not to use it, though the purpose is obvious enough that an agent can infer it from context.

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