Server Quality Checklist

Tool Scores

• subdivision_processC
  2.9/5.0
  Behavior3/5

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

  Annotations already declare readOnlyHint=true, so this is known to be a safe read operation. The description adds 'DEMO,' hinting at limited or non-production data, which provides some extra context beyond annotations. No other behavioral traits (e.g., data scope, return format) are disclosed, but the annotations carry most of the burden here.

  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 extremely concise (just 8 words), which is efficient for a simple tool. However, it lacks structure (no sentences, just phrases). For a tool with only 2 parameters and clear schema, this brevity is acceptable and earns a high score.

  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 simple schema (2 optional string params) and output schema existence (though not shown), the description is minimal but covers the core topic. The 'DEMO' note adds context about reliability. For a simple read-only tool, this is just adequate, but it could mention what the output represents.

  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 100%; both parameters (county, purpose) have descriptions in the schema itself. The tool description adds no additional meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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

  Purpose3/5

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

  The description states 'Land subdivision application process in Kenya. DEMO.' This gives a general topic but lacks an action verb (e.g., 'get' or 'search') and doesn't specify what the tool returns (e.g., applications, statuses). It barely distinguishes itself from potential siblings, but since there are none, it's somewhat acceptable for a vague purpose.

  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 usage guidelines are provided. The description does not mention when to use this tool, prerequisites, or alternatives. With zero guidance, an AI agent must infer usage solely from the name and vague description, which is insufficient for clear decision-making.

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