scoreHookPatterns

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'heuristically' which suggests approximate scoring, but doesn't explain what constitutes a 'hook', how scoring works, what the output format looks like, whether it's computationally intensive, or any rate limits. For a tool that processes up to 20 videos, more behavioral context would be helpful.

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 a single, efficient sentence that gets straight to the point. Every word contributes to understanding the tool's function. While more context would be helpful, what's present is well-structured without unnecessary verbiage.

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 tool with 3 parameters, 0% schema coverage, no annotations, and no output schema, the description is insufficient. It doesn't explain what a 'hook' is, how scoring works, what the output looks like, or provide enough parameter guidance. Given the complexity of video analysis and the lack of structured documentation, the description should do more heavy lifting.

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?

With 0% schema description coverage and 3 parameters, the description provides minimal parameter context. It mentions 'first-30-second hooks' which relates to the hookWindowSec parameter (defaulting to 30 seconds), but doesn't explain videoIdsOrUrls format or what dryRun does. The description doesn't compensate for the complete lack of schema descriptions, leaving key parameters inadequately explained.

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 action ('score') and target ('first-30-second hooks across one or more videos'), with the qualifier 'heuristically' indicating an approximate method. It distinguishes itself from siblings by focusing specifically on hook analysis rather than broader video analysis, playlist handling, or comment processing. However, it doesn't explicitly contrast with similar tools like 'analyzeVideoSet' or 'inspectVideo'.

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 no guidance on when to use this tool versus alternatives. With many sibling tools available for video analysis (analyzeVideoSet, inspectVideo, compareShortsVsLong, etc.), there's no indication of when hook scoring is preferable to other analytical approaches. No prerequisites, limitations, or comparison to similar tools are mentioned.

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