Server Quality Checklist

Tool Scores

• check_adu_eligibilityA
  3.8/5.0
  Behavior3/5

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

  Annotations provide readOnlyHint=true, indicating a safe read operation. The description adds context by specifying the types of ADUs considered (backyard cottage, garage conversion, or addition), which is useful beyond annotations. However, it does not disclose other behavioral traits like rate limits, error handling, or what 'eligible' entails (e.g., regulatory compliance).

  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, efficient sentence that front-loads the purpose without unnecessary details. Every word earns its place by clearly stating what the tool does and the scope of ADUs, making it highly concise and well-structured.

  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 tool's low complexity (one parameter, read-only, no output schema), the description is complete enough for basic use. It specifies the tool's purpose and ADU types, but lacks details on output format or eligibility criteria, which could be helpful given the absence of an output schema.

  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 100%, with the parameter 'address' fully documented as 'Full U.S. property address'. The description does not add any meaning beyond this, such as format examples or validation rules, so it meets the baseline for high schema coverage without compensating further.

  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 specific verb ('Check if a property is eligible') and resource ('ADU - backyard cottage, garage conversion, or addition'), distinguishing it from sibling tools like 'check_flood_risk' or 'what_can_i_build' by focusing on ADU eligibility rather than general property analysis or flood risk assessment.

  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 for checking ADU eligibility, but it does not explicitly state when to use this tool versus alternatives like 'analyze_property' or 'what_can_i_build'. No exclusions or prerequisites are mentioned, leaving the agent to infer context from tool names alone.

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

• check_flood_riskA
  3.8/5.0
  Behavior3/5

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

  Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds value by specifying the data sources (FEMA, EPA, wildfire zones) and scope (U.S. property), which are useful contextual details beyond annotations. However, it does not disclose behavioral traits like rate limits, error handling, or response format, keeping it at a baseline level with annotations covering safety.

  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 highly concise and front-loaded, using a single sentence that efficiently states the tool's purpose and scope without unnecessary words. Every part of the description earns its place by directly contributing to understanding the tool's function.

  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 tool's moderate complexity (single parameter, read-only operation) and lack of output schema, the description is reasonably complete. It covers what the tool does and its scope but could improve by mentioning output details or limitations. With annotations handling safety, it's mostly 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 100%, with the parameter 'address' fully documented in the schema. The description adds no additional parameter details beyond implying it's for a U.S. property, which aligns with the schema. This meets the baseline score of 3 since the schema carries the burden, and no extra semantic value is provided.

  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 with specific verbs ('check', 'covers') and resources ('FEMA flood zone status', 'environmental risk', 'U.S. property'), distinguishing it from siblings like 'analyze_property' or 'check_adu_eligibility' by focusing specifically on flood and environmental risk assessment rather than general analysis or eligibility checks.

  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 for U.S. property risk assessment but does not explicitly state when to use this tool versus alternatives like 'analyze_property' or 'compare_parcels'. It provides context (e.g., 'for a U.S. property') but lacks explicit guidance on exclusions or named alternatives, leaving some ambiguity.

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

• compare_parcelsA
  4/5.0
  Behavior3/5

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

  The annotations already declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds useful context about the comparison scope (zoning, buildability, risk) and target audience (investors), but doesn't disclose behavioral traits like rate limits, authentication needs, or what specific risk factors are considered.

  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 perfectly concise with two sentences that each earn their place: the first states the core functionality, the second provides usage context. It's front-loaded with the essential information and contains zero wasted words.

  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 tool's moderate complexity (multi-property comparison), the presence of readOnlyHint annotation, and 100% schema coverage, the description is reasonably complete. However, without an output schema, it doesn't explain what the comparison results look like or the format of returned data, leaving a minor gap.

  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 100%, so the schema already fully documents the single 'addresses' parameter with its constraints (2-5 U.S. property addresses). The description adds no additional parameter semantics beyond what's in the schema, maintaining the baseline score.

  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 with specific verbs ('compare') and resources ('U.S. properties'), and distinguishes it from siblings by specifying the multi-property comparison scope. It explicitly mentions the comparison dimensions: zoning, buildability, and risk.

  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 provides clear context for when to use this tool ('for investors screening deals') and implies it's for comparing multiple properties (2-5). However, it doesn't explicitly state when NOT to use it or name specific alternatives among the sibling tools.

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

• what_can_i_buildA
  4/5.0
  Behavior3/5

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

  Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds useful context by specifying the scope of project types covered (ADUs, expansions, etc.), but it does not disclose additional behavioral traits such as rate limits, data sources, or response format. With annotations covering safety, a 3 is appropriate as the description adds some value but not rich behavioral details.

  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, efficient sentence that front-loads the core purpose and lists covered project types without unnecessary words. Every part earns its place, making it appropriately sized and well-structured.

  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 tool's moderate complexity (2 parameters, no output schema) and good annotations (readOnlyHint), the description is mostly complete. It covers the purpose and scope well, but it could improve by hinting at output format or data sources. Without an output schema, some gaps remain, but it's adequate for a read-only query tool.

  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 100%, so the schema already documents both parameters thoroughly. The description mentions 'project_type' and 'any' in its coverage list, but it does not add meaningful semantics beyond what the schema provides, such as explaining parameter interactions or usage nuances. Baseline 3 is correct when schema does the heavy lifting.

  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 with a specific verb ('Answer') and resource ('What can I build on this property?'), and it distinguishes itself from siblings by focusing on permitted uses and project types rather than eligibility analysis, risk assessment, or comparisons.

  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 implies usage for determining buildable options on a property, but it does not explicitly state when to use this tool versus alternatives like 'check_adu_eligibility' or 'analyze_property'. It provides clear context but lacks explicit exclusions or named alternatives.

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

• analyze_propertyA
  4.2/5.0
  Behavior4/5

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

  Annotations provide readOnlyHint=true, indicating this is a safe read operation. The description adds valuable behavioral context beyond annotations by specifying the analysis scope (zoning, buildability, constraints), the instant nature of results, and that it returns a link to a full report. No contradictions with annotations exist.

  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 perfectly concise with two sentences that front-load the core functionality and follow with return details. Every word earns its place with no redundancy or unnecessary elaboration.

  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 tool's moderate complexity, rich annotations (readOnlyHint), and 100% schema coverage, the description provides good completeness. It covers purpose, scope, and return format. The main gap is no output schema, but the description adequately describes what's returned (zoning designation, constraints, report link).

  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?

  With 100% schema description coverage, the schema already documents both parameters thoroughly. The description doesn't add significant parameter semantics beyond what's in the schema, though it reinforces the U.S. address scope. Baseline 3 is appropriate when schema does the heavy lifting.

  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 with specific verbs ('Get instant zoning analysis, buildability assessment, and development constraints') and resource ('any U.S. property address'). It distinguishes from siblings by focusing on comprehensive property analysis rather than specific checks like flood risk or ADU eligibility.

  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 provides clear context ('for any U.S. property address') and implies usage for property development analysis, but doesn't explicitly state when to use this tool versus alternatives like 'check_adu_eligibility' or 'what_can_i_build'. It mentions tailoring by persona but doesn't provide exclusion criteria.

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