Hide, unhide or delete a Meta comment

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds valuable context beyond annotations: hide is reversible and invisible to the commenter, delete is permanent and requires confirmation. This clarifies the irreversible nature of delete and the confirmation requirement, enhancing the safety profile.

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?

Two sentences with zero waste. The purpose is stated first, then usage guidance and the critical warning about permanence and confirmation. Every sentence earns its place, and the structure is front-loaded with the most important information.

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 comment moderation tool, the description covers the essential behavioral aspects: actions, reversibility, confirmation requirement, and context (Facebook/Instagram). It doesn't mention output format or error handling, but given the simplicity and that annotations cover the safety profile, it's complete enough for an agent to invoke correctly. Sibling tools provide similar patterns.

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 100% description coverage, including param meanings (action enum with default, pageId when to omit, confirm required only for delete, commentId source). The description reinforces these but doesn't add new parameter-specific semantics beyond what the schema already provides. It does add a behavioral preference (hide over delete) that indirectly affects action choice, but that's more usage guidance.

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 states a specific verb ('Moderate') and resource ('comment on the brand’s Facebook or Instagram post'), and lists the exact actions (hide, unhide, delete). It clearly distinguishes from sibling tools like comment_on_meta_post or reply_to_meta_comment, which serve different purposes.

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?

It provides explicit guidance: 'Prefer hide over delete' with reasoning (reversible, invisible to commenter), and states that delete is permanent and requires confirm:true. While it doesn't explicitly say when to use this tool vs alternatives, it gives clear decision criteria within the tool and implies that for commenting/reply one should use other tools.

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