ghl_business_delete

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

Annotations include destructiveHint: true, already signaling destructive behavior. The description confirms deletion via 'Delete Business' and the DELETE endpoint. However, it does not elaborate on side effects, such as whether the deletion is permanent or cascading effects on related data. The description adds minimal value beyond annotations.

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 short, covering title, endpoint, and OAuth scopes in three lines. While concise, the structure could be improved by separating the title and endpoint details, but it is still efficient with no unnecessary words.

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 that there is no output schema and one required parameter, the description is incomplete. It does not explain response format, error cases, or prerequisites like needing the businessId from another call. The lack of contextual details may hinder effective tool usage.

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?

The input schema has one required parameter (businessId) with no description (0% coverage). The tool description does not explain what businessId is or how to obtain it. In the absence of schema descriptions, the description fails to compensate, leaving the agent without guidance on this critical parameter.

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 title 'Delete Business' and description starting with 'Delete Business' clearly state the tool's purpose. The endpoint and OAuth scopes provide additional context. Among sibling tools like ghl_business_create and ghl_business_get, this tool is uniquely identified as the deletion tool.

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 does not provide guidance on when to use this tool versus alternatives. It mentions OAuth scopes (businesses.write) but does not explain prerequisites, such as obtaining the businessId from a list/get operation. No when-not-to-use or alternative suggestions are given.

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