Mcpier exposes 21 tools with consistent naming (verb_noun pattern) and basic descriptions. However, most parameter descriptions are minimal (5-15 chars), falling well below the 72-char baseline. Input schemas are present but sparse, many parameters lack detailed type info, constraints, or format guidance. Output schemas are undocumented. Error handling is absent from descriptions. The server manages MCP manifests, secrets, and catalogs, a control-plane role, but tool definitions do not guide LLMs on when to use each tool or what to expect in responses.

• Expand parameter descriptions to 50 - 150 chars. Example: 'fetch_secrets' → 'List of secret keys to retrieve (e.g., ["api_key", "db_password"]). Returns only keys that exist; missing keys are silently skipped.'
• Document output schemas for all tools. Example: 'get_manifest returns {servers: [{name, type, config}], version, updated_at}. Use server names to reference in install_mcp.'
• Add error guidance to destructive/complex tools. Example: 'delete_secret: Removes a secret permanently. If the secret is in use by an installed MCP, uninstall that MCP first or the server may fail to start.'
• Clarify mutual exclusivity and defaults. Example: 'resolve_formula: Provide either source (catalog name) OR formula_url (direct URL), not both. If source is omitted, formula_url is required.'
• Add constraints to numeric/enum parameters. Example: 'search_registry: q must be 2 - 100 characters. Returns up to 50 results; use pagination if available.'