Analyze Post

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

Annotations already indicate a safe read-only, idempotent operation, so the description adds value by explaining the actual workflow: importing media, analyzing video frames/carousel images/caption, and returning the full analysis. The credit cost detail is also behaviorally relevant. It does not detail potential failure modes or long-running behavior, but this is not a significant gap.

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 reasonably concise and front-loaded with the core purpose. It covers platforms, return behavior, cost, and usage guidance without excessive fluff. Minor structural awkwardness exists in the first long sentence, but every sentence 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?

For a single-parameter tool with a rich output schema and safety annotations, the description covers all essential context: what is analyzed, which platforms are supported, when to prefer this tool, and the credit cost. An agent has enough information to select and invoke the tool correctly.

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 provides 100% coverage for the single `url` parameter, including the supported platforms. The description adds the media-type nuance (video, image, carousel/slideshow) and explains that the linked content is imported, but the schema already carries most of the parameter meaning.

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 and resource: 'Analyze a social post (video, image, carousel/slideshow) from its link.' It explicitly lists the media types and supported platforms, and differentiates itself from analyze_post_fast by noting that this tool focuses on visuals while the fast version handles script/hook/structure.

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 provides clear when-to-use guidance: 'Use when the visuals are the point.' It also names the alternative tool (analyze_post_fast) and gives a cost-based reason for choosing that alternative, making the selection decision explicit.

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