list_nhi_coverage_rules

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the tool lists data from the local database, without discussing safety (e.g., read-only), auth requirements, or error scenarios. The agent contract adds some guidance on output handling but is insufficient for a full behavioral picture.

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 consists of two concise sentences: the first states the main action, the second provides the agent contract. No unnecessary words; the primary purpose is front-loaded.

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?

Given the low complexity of the tool and the presence of an output schema (so return values are covered), the description is reasonably complete. It includes a key contract for output handling. However, it lacks notes on any response limits or assumptions about database availability.

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?

Schema coverage is 100% and both parameters (locale and output_format) are described with defaults and enums in the schema. The description adds no additional meaning beyond what the schema provides, so it meets the baseline but does not enhance understanding.

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 lists all NHI coverage rules from the local database, using a specific verb ('List') and resource ('NHI coverage rules'). This distinguishes it from sibling tools like get_nhi_coverage or get_nhi_drug_price, which are more focused.

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 includes an 'Agent contract' that guides how to handle the output, but it does not explicitly state when to use this tool versus alternatives or mention any exclusions. Usage context is implied rather than clear.

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