ghl_marketplace_migrate_connection

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

Annotations indicate readOnlyHint=false, so a write operation is expected. The description adds that it validates app configuration, stores credentials safely in encrypted storage, and manages token lifecycle. However, it doesn't disclose idempotency behavior, side effects of repeated calls, or error conditions.

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?

The description is relatively concise, with the main purpose stated upfront. The endpoint and OAuth scopes add technical context but are not redundant. One or two sentences could be removed without losing core meaning.

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?

Given the complexity of the input schema (nested object with many fields) and no output schema, the description lacks details about the return value, error handling, and the precise semantics of 'migration' (e.g., whether it overwrites or creates new). This leaves significant gaps for an agent.

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 the baseline is 3. The description adds some context (e.g., 'validates the app configuration') but does not provide per-parameter guidance beyond what the schema already offers.

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 tool migrates external authentication connection credentials (basic or oauth2) for a specific app and location. It uses specific verbs and resources, and the purpose is distinct from sibling tool names like marketplace_charge or marketplace_get_charges.

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 (migrating external auth credentials) but provides no explicit guidance on when not to use or alternatives. No exclusions or prerequisites are mentioned.

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