Server Quality Checklist

Tool Scores

• plant_detailsA
  4.1/5.0
  Behavior4/5

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

  Beyond the readOnlyHint annotation, the description adds meaningful behavior: fields withheld by the configured plan are returned as null and named in `notes` rather than silently omitted. This is useful transparency about response shape, though it does not cover error cases or other edge behaviors.

  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, front-loaded with the core purpose and immediately followed by the most important behavioral caveat. No filler or repetition of structured metadata.

  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?

  With no output schema, the description compensates by enumerating the profile contents and explaining the null/notes handling for plan-withheld fields. For a single-parameter read-only tool, this is complete and actionable.

  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 single `plant` parameter is already fully described in the schema, including accepted formats and the cost difference between an id and a name. The description adds no additional parameter-level meaning, so the schema carries the burden and baseline 3 is appropriate.

  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?

  Description states exactly what it does: 'Full care profile for one species' and enumerates concrete content areas (sun, water, hardiness zones, mature height, edibility, toxicity, pests). This clearly distinguishes it from siblings like search_plants, planting_window, and companion_check.

  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 when to use it (when you need a full one-species care profile) and the schema parameter explains how to supply a plant via search_plants id or name. However, it does not explicitly state when to prefer plant_details over alternatives or when not to use it.

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

• companion_checkA
  4.4/5.0
  Behavior5/5

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

  Annotations declare readOnlyHint and openWorldHint, but the description adds substantial behavioral detail: the mechanism behind 'bad' (botanical family, pest susceptibility, not folklore) and 'good' (Permapeople listing when configured), plus the return behavior (every matched reason returned, including overridden ones). This goes beyond annotations and provides clear expectations.

  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, front-loaded with the core purpose and then providing mechanism and return behavior. No redundant words; every clause adds value. Excellent conciseness.

  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?

  The description explains the purpose, the logic behind verdicts, and what is returned. With no output schema, it sufficiently covers the expected result behavior. It doesn't state the exact return format, but that's not essential for a read-only check with clear semantics. It's nearly complete, missing only minor format specifics.

  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 descriptions cover both parameters clearly: plant_a as a species id or name, plant_b as the plant to check. The description itself adds no extra parameter semantics, but the mention of 'species id from search_plants' in the schema and the overall context is adequate. Baseline 3 is appropriate given 100% schema 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 the tool checks whether two plants should share a bed, explaining the criteria for 'bad' and 'good' verdicts. It distinguishes itself from siblings (search_plants, plant_details, planting_window) by focusing on companion compatibility, not search, details, or timing.

  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 context implies when to use: to check plant compatibility. The plant_a parameter mentions 'A species id from search_plants', linking to a sibling for finding ids, and the description mentions 'when that source is configured', a prerequisite. However, it doesn't explicitly state when NOT to use it or contrast with alternatives like plant_details.

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

• search_plantsA
  4.4/5.0
  Behavior4/5

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

  Annotations already declare readOnlyHint=true and openWorldHint=true, so the description correctly aligns with those. It adds useful behavioral context beyond annotations by noting that resolving a name costs an extra upstream request, which is important for an agent deciding whether to cache or reuse ids. Without output schema, it doesn't describe pagination or result limits, but with strong annotations, the bar is lower and it provides relevant cost information.

  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, front-loaded with the verb and resource, and each sentence earns its place. The first sentence states purpose and output; the second provides essential usage guidance and a cost note. No fluff or 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 tool's moderate complexity (5 params, all documented in schema), the description covers the core value: search and return ids, plus a key behavioral note about cost. It doesn't discuss pagination or result structure, but without an output schema, that's not required. The description is complete enough for a search-list tool with strong annotations.

  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 all five parameters with descriptions. The description adds little beyond the schema: it mentions 'search by name' but doesn't elaborate on the filter parameters. Per the rubric, since schema coverage is high, baseline is 3, and the description doesn't add extra value beyond the schema's parameter descriptions.

  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 searches the Perenual species catalogue by name and returns candidate species with ids. It distinguishes itself by mentioning that the returned id should be used with sibling tools (plant_details, companion_check, planting_window) rather than passing a name again, which highlights its role as a lookup step.

  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?

  Explicitly guides when to use this tool: to resolve a name into an id, and when not to: avoid passing a name to downstream tools. It names the specific alternatives (plant_details, companion_check, planting_window) and explains the cost of not using the id, providing clear exclusionary context.

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

• planting_windowA
  4.6/5.0
  Behavior5/5

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

  The description clearly discloses the data source ('ten years of observed daily minima') and honestly states that 'no source this server reads publishes those, so they are never guessed' regarding days_to_maturity and frost_tolerance. It also explains that hardiness_zone alone cannot provide frost dates fires. The annotations (readOnlyHint, openWorldHint) are consistent. The description adds substantial 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, dense sentence that efficiently conveys the purpose, data source, and optional parameters. Nofluff, no repetition, and structured logically from core function to optional enhancements.

  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?

  The description covers the main inputs and outputs, data source, and limitations (no guessing of maturity/tolerance). It doesn't specify output format, but that's not strictly necessary. It also doesn't mention error cases, but the schema covers bounds. Overall, it's informative and sufficient for an agent to decide and use the 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?

  All 7 parameters have schema descriptions, with 100% coverage. The tool description adds context by explaining the role of days_to_maturity and frost_tolerance (user-supplied) and the advisory note that they are never guessed. It also clarifies that hardiness_zone is only used when coordinates are unavailable. This goes beyond the schema, enhancing parameter understanding.

  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 starts with a specific verb+resource: 'Frost envelope and hardiness for a location.' It clearly states what the tool derives: last spring frost, first autumn frost, season length, and USDA zone from coordinates. It also differentiates from sibling tools (search_plants, plant_details, companion_check) by focusing on climatic data for planting, making its purpose unambiguous.

  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 gives explicit guidance on when to supply `days_to_maturity` and `frost_tolerance` to obtain transplant and sow-by dates, and notes that these are not sourced from the server. It implies that coordinates are preferred, and that hardiness_zone is only a fallback. It does not explicitly contrast with sibling tools, but the tool's specific inputs (coordinates, plant) and outputs (frost dates, zone) make usage clear.

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