Delete a Google Business Profile Post

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

Goes beyond annotations by stating the action is immediate and irreversible ('CANNOT be undone'), and explicitly advises confirming with the user first. This adds meaningful behavioral context that the destructiveHint and readOnlyHint annotations alone do not fully convey, such as the need for user confirmation and the instantaneous effect.

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?

Four sentences with no redundancy: the first two cover the action and consequence, the third explains how to get the identifier, and the fourth the prerequisite. All sentences earn their place, and the most critical information (irreversibility and confirmation) is front-loaded.

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 delete operation, the description covers the key aspects: effect, irreversibility, source of the post ID, and connection prerequisite. It lacks details about error cases (e.g., post not found) and response behavior, but with no output schema and a simple delete action, these are minor gaps. Could benefit from a note on what happens if the post is already deleted, but overall sufficient.

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 already provides a full description for postId, including the format (accounts/.../locations/.../localPosts/...). The tool description reinforces this by saying 'Pass the full post name from list_google_business_posts' but adds no new information beyond what the schema covers. Therefore, baseline 3 is appropriate.

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 verb 'Remove' and the specific resource ('a Post from the brand’s Google Business Profile listing'), explicitly noting it affects Google Search and Maps. It distinguishes itself from other delete_* siblings by naming the exact platform and linking to list_google_business_posts as the source of the post identifier.

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 usage context: confirms with the user first, instructs to pass the full post name from list_google_business_posts, and states the prerequisite that Google Business Profile must be connected. It does not explicitly mention when-not-to-use or name specific alternatives, but given the specialized nature, the guidance is sufficient.

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