Delete Facebook Comment

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

Annotations already indicate destructiveHint=true. The description adds value by explicitly stating 'Permanent action,' reinforcing the irreversible nature. However, it does not disclose additional behavioral details like authentication requirements beyond the page_id parameter.

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?

Extremely concise: two sentences and an args list. The key information is front-loaded ('Deletes a comment... Permanent action'). No wasted 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?

For a simple delete operation, the description covers the purpose, permanence, and required parameters. It lacks an explanation of response behavior (no output schema) and permissions, but given annotations and schema, it is mostly adequate.

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 has 2 parameters with 50% description coverage (only page_id described). The main description lists the args but provides no explanation for comment_id (e.g., format, how to obtain). It adds minimal meaning beyond the schema.

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 ('Deletes') and resource ('comment on a Facebook Page post'), and distinguishes it from sibling tools like hide or delete post. The addition of 'Permanent action' adds crucial context.

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 implies the tool is for permanent deletion but provides no explicit guidance on when to use it over alternatives like meta_hide_comment. No prerequisites or conditions are mentioned, leaving the agent to infer from the schema.

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