video_verdict

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

With no annotations, the description carries the full behavioral burden, and it discloses only the approval-gating rule (human evidence required). It does not say whether this is a write/mutation, whether existing verdicts are overwritten, what permissions are needed, or any error conditions – substantial gaps for a persistence 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?

It is a single terse sentence with no filler, which is structurally efficient, but the terseness borders on under-specification rather than genuine conciseness given the tool's complexity.

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?

An output schema exists so return values need not be explained, but for a tool with a nested undocumented parameter, no annotations, and an ambiguous purpose, the description is far too thin to let an agent call it 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?

Schema description coverage is 0% for two required parameters, one of which is a nested, open-ended (additionalProperties: true) verdict object. The description supplies no meaning for "verdict" or "project_dir", leaving the most complex input entirely undocumented.

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 says "Persist exact-asset analysis" – the verb "persist" is discernible, but the resource ("exact-asset analysis") is opaque jargon and the nature of a "verdict" is never explained. It does nothing to distinguish this tool from the many evaluation/decision siblings such as video_review_decision, video_review_decide, or video_acceptance_eval.

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?

"Approvals require active human evidence" hints at a precondition for approval verdicts but gives no when-to-use guidance, no exclusions, and no routing to alternative decision-recording tools. An agent cannot infer from this text when to call video_verdict versus any of the review/gate siblings.

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