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

The annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds useful context that the operation is free, accepts posts up to 5 minutes, and returns a URL for sandbox_exec, but it does not explain what is created or persisted, whether authentication is required, or how external social media access is handled.

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 compact and front-loads the key capability, accepted sources, duration limit, return value, cost, and flow. The telegraphic phrasing, especially 'Flow: get_recipe explainer-studio-reference', is slightly cryptic but efficient.

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 one-parameter import tool with no output schema, the description covers the source types, duration limit, cost, return value, and a flow hint. It is still incomplete about what importing actually does, where the reference is stored, side effects, and prerequisites such as authentication or public accessibility.

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 single url parameter has no schema description, so the description must carry its meaning. It helpfully constrains the URL to TikTok, Instagram, or YouTube posts up to 5 minutes, but it does not specify acceptable URL formats, public/private requirements, or whether short links are supported.

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 clearly states that the tool imports a TikTok, Instagram, or YouTube post as a studio reference and returns a URL for sandbox_exec. It is specific about the resource and source platforms, though it does not explicitly distinguish itself from sibling import tools like import_link or import_video.

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 provides a flow hint using get_recipe with explainer-studio-reference and indicates the returned URL is for sandbox_exec, which implies downstream usage. However, it does not explicitly state when to choose this over import_link, import_video, or other sibling tools, nor does it list exclusions.

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