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

Discloses extensive behavioral details beyond annotations: which platforms support keyless access (TikTok, YouTube, Threads, Twitter/X via syndication), which require credentials (Instagram, Reddit, Facebook), Snapchat's lack of keyless support, and LinkedIn quarantine. These are non-obvious and add significant value.

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, front-loaded with the core purpose, followed by a compact enumeration of platform conditions. No redundant or unnecessary text.

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?

Covers core usage and major platform caveats, but omits pagination behavior (cursor) and rate limits. Given the parameter schema documents the cursor and the annotations indicate read-only/idempotent behavior, this is acceptable for a read-only tool.

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?

Adds the 'url OR postId' constraint to clarify mutual exclusivity, which is not fully explicit in the schema. Also mentions the unified Comment[] schema. Since the schema already describes all parameters, this is incremental but meaningful.

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 'Comments / replies on one post' with a specific resource (post) and output ('unified Comment[] schema'), distinguishing it from sibling tools like social_posts or social_search.

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?

Provides clear usage context: 'Provide url OR postId' and enumerates platform-specific credential requirements. It does not explicitly name alternative tools, but the single-post scope and platform caveats imply appropriate usage.

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