Server Quality Checklist

Tool Scores

• build_video_brief_manifestC
  2.7/5.0
  Behavior2/5

  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 mentions the output contents but does not explain how validation is performed, whether the tool can fail (and how errors are surfaced), or any side effects. The term 'validation results' is ambiguous—does it validate the brief itself or aggregated validation data?

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness4/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, concise sentence that front-loads the primary purpose. It is not bloated or redundant. However, it is so brief that it sacrifices substantive content, which is a slight penalty given the tool's complexity.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool has four parameters, a validation focus, no output schema, and no annotations, the description is far too sparse. It does not explain the manifest structure, validation criteria, or how to handle validation failures. The sibling tool validate_video_brief is not referenced, leaving the integration unclear.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters2/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 0%, so the description must compensate for the lack of parameter documentation. It categorizes parameters into 'brief' and 'optional delivery constraints,' which groups title, aspect_ratio, and duration_seconds conceptually, but does not explain their individual purposes, formats, or how they affect the manifest. This is insufficient for a tool with four parameters.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose4/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the tool returns a portable JSON manifest containing the brief, optional delivery constraints, and validation results. It identifies the verb ('return') and the resource (JSON manifest), and implies a distinction from validate_video_brief by including validation results. However, it could be more explicit about the tool's role in building vs. validating.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  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 the sibling validate_video_brief. There is no mention of appropriate contexts, prerequisites, or exclusions. The tool's relationship to validation is only implicit through the phrase 'validation results,' which does not offer actionable usage direction.

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

• validate_video_briefA
  3.7/5.0
  Behavior3/5

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

  With no annotations, the description carries the transparency burden. It discloses that the tool checks for specific signal types, which gives some behavioral insight. However, it does not describe what happens on validation failure, whether the tool is read-only, or what the return format is, leaving room for ambiguity.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, front-loaded sentence that states the action and the specific signal categories without any extraneous information. Every word contributes to understanding the tool's purpose.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness3/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a tool with one parameter and no output schema, the description provides the core purpose and signals checked, but it lacks information about expected output, failure behavior, and usage context. The absence of these details makes it minimally complete but not fully contextual.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The schema documents the only parameter 'brief' with a description, achieving 100% coverage. The tool description does not add any additional semantic detail about the parameter, so the baseline score of 3 applies.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description uses a specific verb ('Check') and resource ('draft video brief') and enumerates the exact signal categories (subject, motion, camera, visual-detail, audio-direction), making its function clear. This distinguishes it from the sibling tool 'build_video_brief_manifest', which likely creates a manifest rather than validating.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines3/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description implies usage when a draft video brief exists and needs validation, but it does not explicitly state when to use this tool versus the sibling 'build_video_brief_manifest'. No exclusions or alternative conditions are provided.

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