Server Quality Checklist

Tool Scores

• get_death_noticeA
  4.1/5.0
  Behavior3/5

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

  With no annotations provided, the description carries the burden of behavioral disclosure. It clearly implies a read-only operation (getting details), but it doesn't mention potential errors (e.g., invalid ID), authentication needs, or that it returns a single record vs. a list. The absence of any side-effect warnings is acceptable for a simple get, but richer context like 'returns 404 if not found' would improve transparency.

  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 that concisely lists what the tool returns. No wasted words, and the structure is clear.

  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 get-by-ID tool with one parameter and an output schema, the description is complete. It covers what the tool does and what fields are included, and the existing output schema handles return value details. There is nothing missing given the tool's simplicity.

  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 fully documents the only parameter notice_id with a clear explanation of its origin (search results or RIP.ie URL). The tool description itself adds no additional parameter semantics. With 100% schema coverage, the baseline is 3, and the description doesn't exceed that.

  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 ('Get') and resource ('full details of a specific death notice'), and enumerates the included content (description, funeral arrangements, photo, family information). It clearly differentiates from sibling tools list_counties and search_death_notices, which are about browsing/searching rather than fetching one record.

  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 a workflow: search first, then get details for a specific notice. The parameter description reinforces this by noting the ID comes from search results or a RIP.ie URL. However, it doesn't explicitly state when not to use this tool or name the alternative for finding IDs, so it falls short of a 5.

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

• search_death_noticesA
  4.4/5.0
  Behavior4/5

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

  With no annotations, the description carries the behavioral disclosure burden. It reveals sorting order (newest first, then surname alphabetically), the requirement of at least one filter, and that filters combine, which are key behavioral traits. It does not mention rate limits, error handling, or pagination details, but these are either in schema or less critical, so the disclosure is strong.

  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 concise and well-structured, with a clear opening statement, a brief usage requirement, a sorting note, and a pointer to a related tool. Every sentence earns its place, and there is no redundant or vocabulary-overloaded content.

  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 (8 params, all optional) and the presence of an output schema, the description provides sufficient context for selecting and invoking the tool. It covers search scope, filter constraints, sorting, and alternatives. It could add a bit more about pagination or edge cases, but the schema and output schema already provide structural details, making this adequately complete.

  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 schema covers all 8 parameters with descriptions, so the baseline is 3. The description adds meaningful semantics beyond the schema by clarifying that filters can be combined and emphasizing that at least one of name, county, or date range should be provided, which is a usage constraint not explicitly encoded in the schema.

  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 opens with a specific verb 'Search' and a concrete resource 'death notices on RIP.ie', making the tool's purpose immediately clear. It also distinguishes itself from sibling tools by explicitly directing users to get_death_notice for full details, clarifying that this tool is for search/filtering rather than retrieving full notices.

  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 clearly states that all filters are optional and can be combined, and that at least one filter should be provided, giving concrete usage guidance. It also points to an alternative tool (get_death_notice) for detailed information, but it does not explicitly say when not to use this tool, though the alternative reference implies a search-vs-detail split.

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

• list_countiesA
  4.5/5.0
  Behavior4/5

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

  With no annotations provided, the description carries the burden. It reveals the tool's read-only nature ('List') and its output (counties and IDs). It adds context about the scope ('all available') and its role in filtering, which is sufficient for a simple reference 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?

  The description is a single, front-loaded sentence with no filler. It efficiently conveys the action, the subject, and the purpose in one concise statement.

  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 zero-parameter reference list, the description is complete: it states the output (counties and IDs) and the use case (filtering death notices). The existence of an output schema means return values are inherently documented, so no further detail is needed.

  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 tool has zero parameters, and the schema is empty (100% coverage vacuously). The description adds semantic value by stating that all counties are listed, implying no filtering input is needed. Baseline for 0 params is 4.

  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 function: 'List all available Irish counties and their IDs'. It specifies the resource (counties) and the purpose (filtering death notices), distinguishing it from sibling tools which search or retrieve notices.

  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 when to use this tool: before filtering death notices, to obtain county IDs. While it doesn't explicitly name alternatives or exclusions, the purpose is clear and the context distinguishes it from search/get tools.

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