ghl_payment_custom_provider_disconnect_config

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

Adds context beyond annotations by noting the potential interruption of live payment collection. Annotations (destructiveHint=false) are consistent since disconnection disrupts but does not destroy data. Includes OAuth scopes and endpoint details.

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 contains redundancy ('Disconnect existing provider config' repeats the purpose) and is not as concise as it could be. It still conveys the necessary information but could be tightened.

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?

Reasonably complete given no output schema: covers the effect, parameters, endpoint, and auth. Could mention recovery but the interruption warning suffices. The tool's role among many siblings is clear.

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 coverage is 100% and both parameters (locationId, body.liveMode) are already well-described in the schema. The description does not add additional semantic meaning or usage details for the parameters.

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 disconnects the custom payment provider's live/test config with a specific verb and resource. It distinguishes itself from sibling tools like create, delete, and get_config by explicitly stating it's a disconnect operation.

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?

Provides clear context on when to use: to disconnect an existing payment config. Includes a warning about interrupting live payment collection. However, it does not explicitly state when not to use or mention alternative tools.

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