get_most_replayed

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It explains what the tool returns (intensity scores and peaks with timestamps) and the view threshold, but doesn't disclose error behavior for videos below 50K views, rate limits, or whether the tool fails gracefully.

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?

Two sentences with the primary purpose front-loaded ahead of the output description and the view requirement. No redundant fluff, though the view requirement could arguably be integrated more tightly into the purpose statement.

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 covers the purpose, deliverable, and a key constraint (view count). Nothing critical is missing for an agent to call it correctly, though error handling for the view threshold is unexplained.

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?

Schema coverage is 100% with a single 'url' parameter described as 'YouTube video URL or video ID'. The description adds no additional parameter-level detail, but the schema is sufficient on its own, so 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?

States a specific verb ('Get') and resource ('most replayed heatmap data for a YouTube video'), and describes the output (intensity scores, top peaks with timestamps). It's clear but doesn't explicitly differentiate from siblings like get_video_metadata or extract_chapters, though the concept is distinct enough.

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?

Provides a useful prerequisite ('Requires 50K+ views') that helps an agent know when the tool will succeed, but gives no guidance on when to choose this over alternatives or when not to use it. The context is implied rather than explicit.

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