connect_ghl_mcp

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions requiring a token and enabling access, but does not disclose whether repeated connections are idempotent, overwrite existing connections, or have side effects. This lack of safety/behavioral detail is a significant gap.

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 with a clear front-loaded verb and resource. The second sentence adds concise value about what the connection enables. No fluff or repetition.

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?

The tool is a simple connection action with few parameters, and the description covers the core purpose. However, with no output schema and no annotations, it does not explain expected return values, persistence, or error scenarios. Acceptable but not rich.

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 description coverage is 100%, so baseline is 3. The description echoes the 'pit' parameter but adds no new semantics beyond the schema. It does give context by explaining that the connection enables access to MCP tools, which is minor added value.

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 verb 'Connect' and specific resource 'GoHighLevel MCP server', with a clear method (using PIT). It distinguishes from sibling tools like disconnect_ghl_mcp and ghl_mcp_status by focusing on establishing the connection.

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?

The description implies when to use it (to enable access to GHL MCP tools), providing clear context. However, it does not explicitly exclude alternatives such as existing connections or reference sibling tools for verification, which would earn a 5.

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