profile_comments_delete

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

The description adds value beyond annotations (which include destructiveHint: true) by explaining the asynchronous nature of the deletion, the return value {accepted: true}, and the constraint that the underlying review cannot be deleted. No contradiction with 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 extremely concise with two sentences. The first sentence states the primary action, and the second adds important constraints and behavior. 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 the tool's simplicity (2 parameters, no output schema), the description covers the core behavior, async dispatch, and return value. However, it could mention error scenarios or prerequisites, but overall it is sufficient for an AI agent.

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 enhances the schema by clarifying that comment_id must be 'Postproxy hashid OR external_id of YOUR reply to remove', emphasizing that it must be the user's own reply. This adds critical meaning beyond the schema's basic description.

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 'Delete your reply to a profile comment', specifying the verb and resource. It distinguishes this tool by noting that it only removes the reply, not the underlying review, differentiating it from sibling tools like comments_delete.

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 provides clear context: it only deletes your own reply, not the underlying review (since Google does not allow businesses to delete reviews). It also mentions asynchronous dispatch. However, it does not explicitly guide when to use this versus other sibling tools like comments_delete or profile_comments_create.

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