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

Annotations already cover the read-only, idempotent, closed-world profile, so the description is free to add substance — and it does: it discloses that auth stays null until sign-in metadata has been checked, that warnings are graded by severity, and that checks which could not run are reported rather than silently omitted. Declaring 'Never a safety rating' also pre-empts a likely misread of the output.

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?

It is compact — one long enumerating sentence plus two short qualifiers — and the schema_version anchor is front-loaded. The trailing 'Never a safety rating' is the most routing-critical clause and would be stronger earlier, but nothing is wasted.

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?

There is no output schema, so the description carries the burden of return-shape disclosure, and it does so by listing the payload's constituent parts and the null-auth state. The one remaining gap is that 'warnings' and 'contradicted claims' are named without saying what entity they attach to, but an agent can still call the tool confidently.

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?

With a single parameter at 100% schema description coverage, the schema already tells the agent that identifier accepts a server name, catalog id, or GitHub repo URL. The description adds nothing further about identifier handling, 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?

The description opens with 'One stable answer (schema_version 1) for connecting an MCP server' and then enumerates the exact contents (remote URL, transport, packages, setup snippets, warnings). This is specific enough that an agent knows it retrieves connection/setup data, though the verb 'get' is implied rather than stated and the framing is more about the answer than the action.

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?

'One stable answer' plus 'Never a safety rating' implicitly separates this from evaluation-oriented siblings like check_before_install, but no sibling is named and there is no explicit when-to-use or when-not-to-use statement. The agent must infer the routing boundary.

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