install_mcp_server

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

No annotations provided. Description does not disclose side effects (e.g., network calls, config changes, permissions). It only states 'Install' without explaining what happens if server already exists or what dependencies are installed.

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?

Description is a single sentence with examples, but the phrasing 'OR link this:' is informal. Could be more structured (e.g., list formats) without increasing length significantly.

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?

No output schema or annotations. Description lacks details on return values, success/failure indications, and operational steps (e.g., cloning, dependency installation, config updates). Incomplete for a installation tool.

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 covers 100% of parameters with description. Description adds concrete examples and clarifies acceptable formats (GitHub URL, shorthand, npm URL), providing value beyond schema.

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?

Description clearly states the tool installs a new MCP server from a GitHub URL or npm package. It distinguishes from sibling tools (repair, search, uninstall) by specifying installation as 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?

Description mentions acceptable input formats (GitHub URL, shorthand, npm URL) and provides examples, but does not explicitly state when not to use or prerequisites (e.g., whether Node.js is required). Sibling names imply clear context.

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