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

There are no annotations, so the description carries the full burden for behavioral disclosure. It does not mention what data is returned, whether this is a read-only operation, any required permissions, or edge cases like invalid URLs or unavailable videos.

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 extremely short, almost a label rather than a sentence. While it is concise, it is under-specified and fails to provide essential information, making it ineffective despite its small size.

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?

With a single parameter and no output schema, the description still needs to clarify what 'details' means and how the result is structured. There is no information about return values, use cases, or differentiation from similar tools, leaving the tool contextually incomplete.

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 has 100% coverage for the single 'url' parameter, which is described as 'YouTube video or short URL'. The description adds no additional semantic value, but since the schema already sufficiently documents the parameter, baseline 3 is appropriate.

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 "Video/Short Details" essentially restates the tool name without a clear verb or resource. It fails to specify whether this retrieves metadata for a single video, a short, or both, and does not distinguish it from similar sibling tools like scrapecreators_video_info or scrapecreators_channel_shorts.

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?

No guidance is provided on when to use this tool or when to prefer an alternative. With dozens of sibling tools covering videos, shorts, and details, the description gives no context for selection.

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