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

With no annotations, the description carries full behavioral burden and does well: it discloses read-only public access, best-effort nature, server-side execution, and the specific failure mode of IG/FB blocking server IPs with a 'needs_proxy' status plus remedy. It doesn't detail response shapes or error handling, but the key behavioral traits are clearly surfaced.

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 description is dense and front-loaded with the core purpose, then platform details, then proxy caveat. The bilingual repetition adds slight redundancy but remains compact and useful; every major point earns its place.

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?

Given there is no output schema, the description covers expected return categories per platform and the notable 'needs_proxy' status. It lacks a concrete response structure or explicit error codes, but it gives enough for an agent to select and invoke the tool correctly in most cases.

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% with detailed parameter descriptions, so the baseline applies. The body description adds platform-specific value like Facebook accepting numeric UID, full profile URLs, and proxy guidance, but most parameter semantics already live in the schema itself.

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?

Description opens with a specific verb and resource: 'Deep profile lookup for one social account,' and enumerates exactly what data is returned per platform (Instagram/TikTok followers, bio, verified, media; Telegram title, members; Facebook live/dead + avatar). This clearly distinguishes it from unrelated siblings like buy_product or check_live_facebook.

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 context: server-side, best-effort, read-only, free, and per-platform behavior. It also gives conditional guidance for IG/FB proxy use and the 'needs_proxy' status, though it does not explicitly name alternatives or when-not-to-use this tool versus the related check_live_facebook.

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