get_mcp_install_config

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

With no annotations, the description fully discloses behavior: returns dict with config (may be null if missing), available_clients, install_command, page_url. It transparently explains the fallback behavior of trying different clients.

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?

Well-structured with summary, args, returns, and usage tip. Every sentence adds value, though slightly verbose. Could be trimmed but remains 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?

Thoroughly covers inputs, outputs, edge cases (null config), and real-world usage guidance (path to config file). No output schema or annotations, but description compensates fully.

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?

Despite 0% schema coverage, description explains both parameters: slug (MCP server slug from search, with example) and client (list of values, default). Adds meaning beyond the minimal schema definition.

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 it 'Get a ready-to-paste install config for a specific MCP server and client,' using a specific verb and resource. It distinguishes from sibling tools like get_mcp_details or search_mcp_servers by focusing on configuration retrieval.

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 'Use this AFTER finding an MCP via search,' providing clear context for when to invoke. It also advises on showing the config snippet and config file path. Lacks explicit 'when-not-to-use' but the context is sufficient.

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