Server Quality Checklist

Tool Scores

• search_spacesA
  4.2/5.0
  Behavior4/5

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

  Beyond the readOnlyHint annotation (safe read operation), the description discloses useful behavioral traits: results are paginated, location data is approximate/obfuscated, and the returned set is limited to public/published spaces. It also states the exact fields included in summaries. This adds valuable context beyond the annotation, though it does not cover potential edge cases like empty results or error responses.

  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, information-dense sentence that front-loads the core purpose and then lists the return fields. It avoids redundancy and every clause earns its place, 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 there is no output schema, the description compensates by specifying exactly what the returned summaries include (name, venue type, capacity, pricing, photos, location). It also notes pagination and obfuscated location. While the tool has 9 parameters, the 100% schema coverage handles parameter details. It does not mention ordering (e.g., by distance) or pagination mechanics, but the description is largely complete for a search 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?

  The input schema has 100% description coverage for all parameters, so the description does not need to compensate. The description adds no parameter-specific semantics beyond what the schema already provides. According to the rubric, baseline 3 is appropriate when schema coverage is high and the description adds no extra meaning.

  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: searching published spaces on Espaciarte around a geographic point with optional filters. It specifies the resource type (event venues, workspaces, studios) and the output (a paginated list of summaries). This distinguishes it from the sibling get_space_details, which presumably returns full details, by explicitly mentioning 'summaries'.

  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 use: when searching for published spaces on Espaciarte by location and filters. It does not explicitly name the alternative get_space_details, but the phrase 'public space summaries' implicitly suggests that full details are available elsewhere. While it lacks an explicit 'when not to use' statement, the scope ('published spaces', 'public') offers some exclusion criteria.

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

• get_space_detailsA
  4.3/5.0
  Behavior4/5

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

  The readOnlyHint annotation already indicates a safe read operation. The description adds that the space must be 'published' and that the details are 'public', which clarifies access constraints and what the result contains. It stops short of describing error behaviors, but overall adds value beyond the annotation.

  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 front-loaded sentence. It starts with the verb and resource, then efficiently lists the key data points without redundant words. No filler.

  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?

  For a simple one-parameter fetch with no output schema, the description adequately explains what the tool returns by enumerating the fields. It also distinguishes from the sibling tool and provides enough context for an agent to use it 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?

  Schema coverage for the single parameter is 100%, with an explicit description ('Space id, from a prior search_spaces result item'). The tool description does not add additional parameter-specific context, so the baseline of 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?

  The description uses a specific verb ('Fetch') and resource ('full public detail of one published Espaciarte space by id'), and enumerates the contained fields (description, rules, photos, etc.). This clearly distinguishes it from the sibling search_spaces, which presumably returns a list/summary.

  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 after search_spaces by noting the id comes from 'a prior search_spaces result item' in the parameter schema. It doesn't explicitly name alternatives or exclusions, but the context of fetching full detail for a single space vs. searching is clear.

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