list_counties

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.

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.

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.

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.

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.

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.