scoreHookPatterns

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

With no annotations, the description carries full burden but omits critical behavioral details: whether results are persisted (implied by dryRun parameter but not explained), what the score format/range is, or whether this requires specific permissions. Only provides latency estimates ('~3-10s').

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?

Extremely concise with only two components: functional description and performance estimate. Front-loaded with the action. The bracketed timing notation is slightly cryptic but efficient. No wasted words.

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 0% schema coverage, no annotations, and no output schema, the description leaves significant gaps: parameter semantics are largely undocumented, return value structure is unknown, and side effects (suggested by dryRun) are unexplained. Needs expansion for a 3-parameter mutation-capable tool.

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 has 0% description coverage. The description mentions 'first-30-second' which hints at the default hookWindowSec behavior, but fails to explain videoIdsOrUrls format expectations or the critical dryRun parameter (which likely controls persistence). Insufficient compensation for missing schema documentation.

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 specific action ('Heuristically score') and target resource ('first-30-second hooks across one or more videos'). The specificity of 'hooks' distinguishes it from general analysis siblings like analyzeVideoSet, though it doesn't explicitly contrast with them.

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 no guidance on when to use this tool versus alternatives like analyzeVideoSet or inspectVideo. The bracketed timing '[~3-10s, ~1s per video]' suggests performance characteristics but doesn't indicate appropriate use cases or prerequisites.

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