check_server

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

Describes key behaviors: launches server, checks capabilities, saves artifact. Explains deep and security parameters' effects. No annotations, so description carries burden; it is thorough but could mention if there are any side effects.

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 plus an example; no fluff. Purpose front-loaded, each sentence adds information. Highly efficient.

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 testing tool with 4 parameters and no output schema, description explains all necessary usage, example, and parameter purposes. Complete for its complexity.

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 coverage is 100%, providing baseline. Description adds value by explaining deep and security flags beyond schema descriptions, and gives a concrete example.

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 clearly states the tool tests a specific MCP server before installation or after update, with actions: launch, check capabilities, save artifact. It distinguishes from siblings by focusing on testing rather than scanning or scoring.

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?

Explicitly says when to use (pre-install, post-update), providing clear context. Lacks explicit when-not-to-use or alternatives, but the purpose is well-defined.

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