ghl_social_delete_like

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds valuable context: the ID is the Highlevel comment ID (not native), it works for any comment level, and platform limitations. This goes beyond the annotations to clarify behavior.

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 and front-loaded with the action. The first line ('Unlike a comment') somewhat repeats the title (which is null), but overall it's well-structured with clear sections for platforms and endpoint.

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?

With no output schema, the description adequately explains the input parameters and constraints. However, it lacks any mention of the return value (e.g., empty body on success) or error cases, making it slightly incomplete for a tool with no output schema.

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?

Input schema coverage is 100%, so the schema already documents all three parameters thoroughly. The description repeats some parameter info (e.g., id source, platform enum) but adds the endpoint and version header. It doesn't provide new meaning beyond the schema.

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 action ('Unlike a comment' and 'Remove a like') and the resource (comment), with specific details about the ID type and supported platforms. It implicitly distinguishes from the sibling 'create_like' by being the removal counterpart.

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 lists supported platforms and explicitly notes Instagram is not supported, which helps avoid errors. However, it does not provide guidance on when to use this tool versus 'create_like', prerequisites (e.g., must have liked first), or when not to use it.

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