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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds substantial behavior beyond them: the platform-first-then-record ordering that prevents false deletion reports, cascade deletion of nested replies on Facebook/Instagram/Threads/LinkedIn, and the irreversibility note that a deleted comment cannot be restored. This is exactly the extra operational context an agent needs for a destructive call.

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 core action is front-loaded in the first sentence, and each subsequent sentence carries distinct, non-redundant information (ordering guarantee, cascade behavior, permission check, irreversibility). It is dense but appropriately sized for a destructive, multi-platform operation.

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 fully covers what matters: preconditions (owning the post, delete_any capability), the safety semantics of the deletion, cross-platform cascade behavior, and irreversibility. Nothing an agent needs to call this destructive tool correctly is missing.

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 100% and both parameters are documented there (post_id, comment_id with its chirpie_list_comments origin). The description reinforces that comment_id comes from chirpie_list_comments and ties post_id to 'a post you published,' but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 first sentence states a specific verb and resource with scope ("Delete a comment on a post you published"), which is more precise than the bare title. It does not, however, explicitly differentiate itself from the sibling chirpie_hide_comment, leaving the delete-vs-hide distinction to be inferred.

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 gives real context for when the call is legitimate: the comment must be on a post you published, and capabilities.delete_any from chirpie_list_comments determines whether deleting someone else's comment is permitted. It stops short of naming exclusions or the hide_comment alternative, so the guidance is clear but not complete.

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