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

With no annotations, the description carries the burden of behavioral disclosure. It does reveal return content (follower counts, bio, verification, `extra`) and accepted input kinds, but it does not mention auth requirements, rate limits, error behavior, or which platforms are excluded.

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 long but justified by seven platforms; the general rule is front-loaded, then each platform is covered compactly. The semicolon-heavy style is dense but readable.

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 the high complexity (7 platforms, 0% schema coverage, no output schema), the description provides substantial guidance on input construction and mentions key return fields. It stops short of a full output shape or handling of ambiguous cases like the post-URL behavior for a user-profile 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?

Schema coverage is 0%, and the description fully compensates by enumerating valid `id` formats for each platform, including handles, URLs, shortcodes, post IDs, and even short links. This is exactly the domain semantics the schema leaves out.

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?

States a specific resource ('A user's profile') and the key data returned (follower counts, bio, verification, platform extras), which distinguishes it from siblings like get_post or get_comments. The extensive per-platform notes slightly blur the line by accepting post URLs, but the core purpose remains clear.

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 gives concrete identifier formats for each platform and implies when to use the tool with those inputs, but it never explicitly says when not to use it or names alternatives like get_post for actual post retrieval. Usage context is implied rather than explicit.

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