get_most_replayed

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

Without annotations, the description carries the full burden. It discloses a behavioral constraint (50K+ views required) and what data is returned, but does not state whether the operation is read-only, has side effects, or requires specific authorization. It is adequate but lacks completeness.

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 two sentences, directly stating the purpose, output, and requirement. Every sentence adds value; no redundancy or unnecessary information. Front-loaded with the primary action.

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?

Given the tool's simplicity (one parameter, no output schema), the description covers the essential aspects: what it does, what it returns, and a key prerequisite. It could include more detail on output format or example, but is largely sufficient for an agent to understand usage.

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 covers 100% of the parameter descriptions, so the description adds no extra semantic detail about the 'url' parameter beyond what the schema provides. Baseline score of 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 clearly states the tool retrieves 'most replayed' heatmap data for a YouTube video, specifying the returned items (intensity scores, top peaks with timestamps). It distinguishes itself from sibling tools like get_video_metadata or extract_chapters by focusing on replay 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 provides an explicit prerequisite (50K+ views), offering some context for when the tool is applicable. However, it does not mention alternative tools or situations when not to use it, leaving the agent to infer usage from the prerequisite alone.

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