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

Annotations only state destructiveHint=true and openWorldHint=true generically; the description adds substantial context beyond them: TikTok's limited deletion scope, YouTube's rejection of non-owned comments, the irreversibility of YouTube deletes, and the banAuthor side effect that also bans the commenter. This is exactly the kind of behavioral detail annotations cannot convey.

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?

Front-loads the core action, then adds platform-specific rules, then the confirmation caution. Every sentence carries real information, though the run-on YouTube clause is dense enough to warrant a slightly less than perfect score.

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 destructive, credential-scoped tool with no output schema, the description covers platform divergence, side effects, irreversibility, and user-confirmation expectations. Nothing an agent needs to invoke it safely 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 60%, and the description compensates by explaining the non-obvious banAuthor parameter ("true" also bans that commenter). It also clarifies how platform affects behavior, though it does not spell out the platform enum values or the accountId/profileId linkage beyond what the schema provides.

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?

Opens with a specific verb+resource ("Permanently delete a comment") and goes further by spelling out the platform-specific scope of deletion. An agent can immediately distinguish this destructive single-comment operation from siblings like update_comment, list_comments, or reply_to_comment.

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?

Gives clear when-to-use context per platform and names an alternative action ("hide other people's comments instead" on TikTok) plus an explicit confirmation requirement. It stops short of formally mapping when to prefer update_comment or reply_to_comment over deletion, so not a full 5.

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