get_nhi_data_status

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

No annotations exist, so description carries full burden. It declares the tool inspects without forcing a download, implying read-only. The contract details how to treat the output. However, it does not mention side effects, auth needs, or caching behavior. Still, it is clear about non-destructive nature and output handling.

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?

Two sentences: one for core purpose, one for agent contract. Front-loaded, no wasted words. Every sentence adds value.

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?

With output schema present, description need not explain return values. Covers purpose, parameters, and behavioral contract. For a simple inspection tool, this is fully complete.

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%, so description adds minimal meaning beyond the schema. Parameters locale and output_format are already clear from schema. The description's focus on output handling does not enhance parameter understanding. Baseline 3 is appropriate.

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 states 'Inspect the Taiwan NHI official index freshness, row count, local path, and upstream dataset URL' – a specific verb and resource. It distinguishes from a download action and is distinct from sibling tools like get_nhi_coverage or get_nhi_drug_price.

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 'without forcing a download,' implying when to use this inspect tool. The 'Agent contract' provides explicit guidance on handling results (use structuredContent, preserve fields, do not infer). Does not explicitly exclude alternatives or state when not to use, but provides clear context.

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