Understand Social Post

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

No annotations are provided, so the description carries the behavioral burden. It discloses that the tool uses multimodal AI over actual video/images, includes the thumbnail, supports a list of platforms, and has a metered credit cost (1 free use, then 6 credits). It could mention auth or side effects, but the operation is clearly analytic and read-only in intent.

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 but each sentence earns its place: core action, supported platforms, cost, and when-to-use guidance. It is slightly long and could be tightened, but there is no wasted filler.

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 appropriately enumerates what the tool returns. It also covers supported platforms, credit cost, and the strategic alternative. It does not explain error behavior or how the focus parameter interacts, but the schema covers the parameter and the tool's purpose is sufficiently complete.

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 already describes both parameters: url as a full public post URL and focus as an extra instruction. Schema coverage is high, so the baseline applies. The description adds context about the analysis but does not add real per-parameter semantics beyond the schema.

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+resource: import a social post URL and understand it with multimodal AI over the actual video/images. It also lists concrete outputs (summary, hook strength, viral triggers, format breakdown, variation ideas) and explicitly distinguishes itself from analyze_post, the sibling focused on strategy.

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 explicitly says 'Use when you need a factual description of what physically happens on screen' and names the better default alternative: 'analyze_post is the better default for strategy.' This gives an agent a clear selection rule against at least one sibling.

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