get_most_replayed

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses the prerequisite (50K+ views) and the nature of the output (intensity scores and top peaks with timestamps), which is meaningful context beyond the schema. It does not detail exact output fields or error behavior, but coverage is solid for a read-only data retrieval tool.

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?

Three sentences with no filler; the purpose, output, and key constraint are all included and front-loaded. 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 no output schema, the description explains what data is returned (intensity scores, top peaks, timestamps) and the critical prerequisite. It could add more detail about the exact response shape, but the agent has enough to invoke and interpret the result 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 already describes `url` as 'YouTube video URL or video ID' with 100% coverage. The description adds little beyond reinforcing that the tool operates on a YouTube video, so it does not materially improve parameter understanding.

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 uses a specific verb ('Get') with a clear resource ('most replayed heatmap data for a YouTube video') and explains what it returns. It is easily distinguishable from sibling tools like get_video_metadata or extract_chapters because it uniquely targets rewatch heatmap data.

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 clearly states a key usage constraint: 'Requires 50K+ views.' This helps an agent decide whether the tool is applicable for a given video. It does not explicitly name alternative tools, but no sibling directly overlaps with this heatmap functionality.

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