Get Social Media

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds meaningful behavior beyond annotations: it returns an inline thumbnail image and consumes 1 orchyn credit with a free-credit allowance for new users.

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 appropriately compact and front-loaded with the core purpose and output. It packs platform list, return fields, thumbnail behavior, credit cost, and usage guidance into a short space; a minor formatting issue is the missing space after 'new users).Use'.

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 tool has only one parameter, a high-coverage schema, an output schema, and strong annotations, the description covers all necessary decision points: supported platforms, returned data, credit cost, and when to choose the sibling tool. No critical guidance is missing.

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 schema fully documents the single url parameter, so the baseline is 3. The description adds value by specifying the accepted platform URL types (TikTok, Instagram, YouTube, X/Twitter, Douyin, Xiaohongshu, Bilibili), which helps an agent validate acceptable inputs.

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 names the specific action ('Fetch a social post's media') and the exact resource (post URLs from seven named platforms), and itemizes the returned fields. It also distinguishes itself from the sibling analyze_post_fast by framing itself as returning raw facts and media, not interpretation.

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 explicitly states when to use the tool: 'Use when you need the post's facts and media and nothing more'. It also names the alternative, analyze_post_fast, for interpreted results, giving an agent a clear routing decision.

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