Server Quality Checklist

Tool Scores

• prepare_team_reviewA
  3.7/5.0
  Behavior4/5

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

  Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is clear. The description adds behavioral context: 'It inventories artifacts and includes deterministic manifest issues when a manifest is available.' This goes beyond the annotations without contradicting them.

  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 two sentences long, each conveying essential information. The first sentence states the core action, and the second adds relevant detail. No superfluous text.

  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?

  Given the tool has no required parameters and no output schema, the description covers the main behavior. However, it lacks details about the output (e.g., what the review brief contains) and does not mention any prerequisites or subsequent steps. This is adequate but not fully comprehensive.

  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?

  Schema description coverage is 50% (manifestPath has a description, goal does not). The description adds context about using a manifest and inventorying artifacts, which clarifies manifestPath's role. However, it does not explain the 'goal' parameter beyond its default value. This provides moderate added value but not full compensation.

  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 explicitly states the tool builds an 'evidence-first review brief with four parallel roles' for a specific context ('Antigravity /teamwork-preview'). This is a specific verb-resource combination that clearly distinguishes it from sibling tools (discover_map_artifacts, inspect_map_views, validate_map_manifest).

  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?

  No explicit guidance is given on when to use this tool versus its siblings. For example, it does not mention prerequisites (e.g., needing a manifest discovered) or scenarios where this tool is appropriate. The description only states what it does, not when to use it.

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

• validate_map_manifestA
  3.9/5.0
  Behavior4/5

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

  Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds value by listing the specific quality gates performed, providing richer behavioral context beyond the annotations.

  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 sentence that efficiently enumerates all validation checks without redundancy or filler. Every listed item earns its place.

  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?

  The description explains what the tool does comprehensively, but lacks information about the output or return value. Since there is no output schema, the agent may need to know whether results are detailed or a simple pass/fail.

  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 input schema fully documents the single parameter 'path' with description. The tool description adds no additional semantic meaning to the parameter beyond what the schema already provides, meeting the baseline for high coverage.

  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 clearly states 'Runs deterministic map quality gates' and enumerates specific checks (schema, bounds, unique ids, etc.). The verb 'validate' in the name is reinforced, and the tool is distinct from siblings which focus on discovery, inspection, and review.

  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 use when a manifest needs validation, but no explicit guidance on when to choose this over siblings or prerequisites. The agent must infer context from the sibling names.

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

• inspect_map_viewsA
  4.2/5.0
  Behavior4/5

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

  Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds value by stating the output is image content and listing specific visual checks, which enhances transparency beyond the annotations.

  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 two focused sentences: the first describes the output and inspection capability, the second states the prerequisite. No wasted words; front-loaded with key information.

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

  Completeness4/5

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

  For a simple read-only tool with two parameters and no output schema, the description covers the output format, prerequisite, and inspection purpose. It lacks detail about the focus parameter and error handling, but is sufficient for typical use.

  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?

  Schema coverage is 50% (only 'paths' documented in schema). The description adds some context by listing inspection areas, hinting at the purpose of the 'focus' parameter, but does not explicitly explain parameter semantics or defaults, leaving room for ambiguity.

  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 clearly states it returns viewport captures as image content for visual inspection of specific map quality aspects like seams and collisions. It distinguishes itself from siblings by explicitly linking to discover_map_artifacts as the source of valid paths.

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

  Usage Guidelines4/5

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

  The description explicitly requires paths to come from discover_map_artifacts, providing a clear prerequisite. While it does not list when to avoid using the tool, the context implies it is for visual inspection after discovering artifacts.

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

• discover_map_artifactsA
  4.7/5.0
  Behavior5/5

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

  Annotations already declare readOnlyHint and idempotentHint as true. The description adds concrete behavioral context by specifying it inventories 'screenshots, manifests, and world-generation stage outputs' and limits scope to the configured project root, which enhances transparency beyond annotations.

  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 two sentences: the first states the purpose and scope, the second provides a usage directive. No extraneous words, all information is pertinent.

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

  Completeness5/5

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

  Given the tool has no parameters, no output schema, and annotations cover safety, the description fully addresses what the tool does and when to use it. It provides enough context for an agent to invoke it correctly as a first step.

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

  Parameters4/5

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

  There are zero parameters and schema coverage is 100%. Per guidelines, baseline for 0 params is 4. The description adds overall context but there are no parameters to describe.

  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 clearly states it is a 'read-only inventory' of specific artifacts (screenshots, manifests, stage outputs) within a defined scope (Animal Engine project root). It distinguishes from siblings by suggesting it be called first, implying a discovery step before inspection or validation.

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

  Usage Guidelines4/5

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

  The description explicitly says 'Call this first,' providing clear guidance on when to use the tool. It lacks explicit 'when not to use' statements, but the context of siblings implies other tools are for subsequent steps.

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