ghl_social_bulk_delete_planner_posts

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

There is a clear contradiction: the description says the tool deletes posts (destructive action), but the annotations set destructiveHint=false. Additionally, the description states 'It will only get deleted in CRM database' which hints at scope but is vague. The contradiction undermines transparency.

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 but includes an awkwardly phrased note and an endpoint line that may be extraneous. It could be streamlined while retaining key information.

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?

The description lacks details on success/error responses, output format (no output schema), and precise behavioral scope (only CRM deletion). The contradiction with annotations further reduces completeness. For a bulk delete operation, more context is needed.

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 description adds one useful detail beyond the schema: the maximum of 50 post IDs per request. However, the schema descriptions for locationId and postIds are poor ('Requested Results'), and the tool description does not elaborate on the structure of the body or the locationId. With 100% schema coverage but weak schema descriptions, the added value is moderate.

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 bulk deletes social planner posts by providing a list of post IDs. It specifies the action (bulk delete) and the resource (social planner posts), and the mention of 'clearing up large numbers of posts efficiently' distinguishes it from single-delete alternatives like ghl_social_delete_post.

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 indicates the tool is useful for efficient bulk deletion and notes a maximum of 50 posts per request. However, it does not explicitly state when to use this tool over alternatives (e.g., single delete) or provide exclusion criteria. The guidance is minimal.

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