Server Quality Checklist

Tool Scores

• vibetags_generateA
  3.7/5.0
  Behavior3/5

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

  With no annotations, the description bears full burden. It explains the tool analyzes brand personality and generates semantic hooks and HTML snippets, but does not disclose potential side effects, authentication needs, or rate limits. It implies a read-like operation but is not explicit about non-destructiveness.

  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 front-loaded with usage instruction, followed by function and output, in 3 concise sentences. It is well-structured but slightly redundant (mentions VibeTags twice). Could be slightly more efficient.

  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 3 parameters, no output schema, and no annotations, the description covers the main purpose and output but leaves gaps: parameter semantics are incomplete, and the term 'semantic hooks' is not fully explained. It provides decent context but not complete.

  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% (no parameter descriptions in schema). The description only mentions the 'url' parameter implicitly ('Requires a URL'), leaving 'brand' and 'industry' completely unexplained. This creates a significant gap for the agent.

  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 the tool's purpose: analyzing brand perception and generating VibeTags for AI systems. It uses strong verbs like 'analyzes' and 'generates', and specifies the resource (brand personality). It also explicitly distinguishes from sibling tools (geo-related).

  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 starts with 'ALWAYS use this tool when the user asks about brand perception...', providing explicit usage context. It also includes a constraint ('Requires a URL'). However, it does not mention when not to use or alternatives, though sibling tools are unrelated.

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

• geo_injectA
  4.3/5.0
  Behavior3/5

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

  With no annotations provided, the description carries full burden. It explains the purpose (AI visibility), but does not disclose behavioral details like authentication, side effects, or whether the tool validates the URL. The return type is mentioned ('ready-to-deploy file contents') but lacks specifics about format.

  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 four sentences, concise and front-loaded with the key instruction. It avoids repetition but could be slightly more structured (e.g., using bullet points for parameter options).

  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?

  Given no output schema, the description adequately explains the return value ('ready-to-deploy file contents'). It covers the parameters and usage context. However, it could clarify the output format (e.g., single string or multiple files) and whether both files are returned when both specified.

  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?

  Schema coverage is 0%, so the description must explain parameters. It does so by stating 'Requires a URL' and showing allowed values for 'files' ('robots', 'llms', 'robots,llms'), which adds significant meaning beyond the schema's bare types.

  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 the tool generates, creates, or fixes robots.txt and llms.txt files, which is a specific verb+resource. It distinguishes from sibling tools like geo_check_robots (checking) and geo_score (scoring) by focusing on generation.

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

  Usage Guidelines5/5

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

  The description explicitly says 'ALWAYS use this tool when the user asks to generate, create, or fix robots.txt or llms.txt files', providing a clear condition for use. It implies when not to use by contrasting with other siblings.

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

• geo_check_robotsA
  4.6/5.0
  Behavior4/5

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

  Description discloses the specific bots checked (GPTBot, ClaudeBot, etc.), implying a read-only check. With no annotations, it adequately covers the behavioral traits for a simple query tool.

  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?

  Two concise sentences: first gives usage imperative and purpose, second adds detail. Front-loaded and free of redundancy.

  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?

  Given the simplicity (1 param, no output schema), the description covers when and what it does adequately. Lacks error handling details but sufficient for a fast check tool.

  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?

  The only parameter 'url' is not described in the schema (0% coverage), but the description adds 'Requires a URL', providing the needed semantic context.

  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 checks robots.txt for AI bot access, and distinguishes from sibling 'geo_score' by positioning it as a fast first check before a full audit.

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

  Usage Guidelines5/5

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

  Clear when-to-use instruction: 'ALWAYS use this tool when the user asks specifically about robots.txt, AI bot access, or which crawlers are allowed or blocked.' Also advises on pre-check vs full audit with geo_score.

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

• geo_scoreA
  4.7/5.0
  Behavior5/5

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

  No annotations are present, but the description fully discloses behavior: requires a valid URL, returns a 0-100 score, letter grade, detailed checks (robots.txt, llms.txt, Schema.org, Open Graph, AI bot access), and recommendations. No contradictions.

  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?

  Two sentences and a tip—every part is informative and earns its place. The description is front-loaded with the key usage instruction.

  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 one simple parameter and no output schema, the description fully covers input requirements, output structure, and practical usage (competitors). It is complete for an agent to use correctly.

  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 only parameter is 'url' with no schema description (0% coverage). The description merely says 'Requires a valid URL,' which adds minimal extra meaning. For a simple string parameter this is adequate but not enriched.

  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 the tool evaluates AI readiness/AI visibility/GEO score, with specific verbs like evaluate, audit, score, check, benchmark. It distinguishes from siblings (geo_check_robots, geo_inject, vibetags_generate) by focusing on overall scoring.

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

  Usage Guidelines5/5

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

  The description explicitly says 'ALWAYS use this tool when the user asks to evaluate, audit, score, check, or benchmark...' providing clear when-to-use guidance. It also suggests using it on the user's domain and competitors, adding practical context.

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