setup_ghl_mcp

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

No annotations provided, so description must cover behavior. It discloses validation, writing credentials to file, need for restart, and optional Firebase setup. Lacks details on overwriting existing config or error handling, but sufficient for a setup tool.

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?

Three sentences, front-loaded with purpose, no fluff. Every sentence adds essential information about what the tool does, what to do after, and optional variants.

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?

Complete for a setup tool: explains required vs optional fields, post-setup steps, and ties to other tools (enable_workflow_builder). No output schema needed; the description covers the expected workflow.

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?

All 9 parameters have schema descriptions, but the description adds value by explaining the 'one-paste' vs 'manual' Firebase paths and providing context for location IDs and API keys, enhancing understanding beyond the 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?

Clearly states 'First-run setup for GHL Command MCP' with specific verbs 'validates' and 'writes'. Distinguishes from siblings by being a one-time setup, while siblings are for capturing Firebase, version info, or license requests.

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 'First-run setup' and 'Restart Claude after this completes'. Also notes optional Firebase fields and suggests using enable_workflow_builder later, but does not explicitly state when not to use or compare with siblings.

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