ghl_association_delete_relation

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

Annotations already indicate destructive behavior and idempotency, but the description adds only the endpoint and OAuth scopes, which are technical details rather than behavioral context. It does not disclose consequences like cascading deletions or required permissions beyond scopes.

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 and includes necessary technical details (endpoint, scopes) without excessive fluff. It is front-loaded with the title, though some technical content may be unnecessary for an agent. Still, it is reasonably concise.

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?

For a destructive tool with no output schema and partial parameter descriptions, the description lacks completeness. It does not specify what happens after deletion, any error conditions, or how relationId should be obtained. Annotations help but leave gaps.

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 50%: locationId has a description ('Your Sub Account's ID'), but relationId has no description and is not explained in the tool description. The description does not add meaning beyond the schema, which already partially covers locationId but leaves relationId ambiguous.

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 merely restates the tool's name as 'Delete Relation' and provides endpoint details, but fails to clarify what a 'relation' is in the context of associations. It does not distinguish this tool from siblings like ghl_association_delete or ghl_association_create_relation.

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?

No guidance is provided on when to use this tool versus alternative tools such as ghl_association_delete. The description lacks any context about prerequisites, typical use cases, or scenarios where this operation is appropriate.

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