export_reg_get_tariff_items

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

The annotation already declares readOnlyHint=true, and the description's '取得します' is consistent. The description adds the use-case context but does not disclose additional behavioral aspects such as return format, pagination, or error handling. For a read-only getter with annotation coverage, this is adequate but not rich.

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 concise sentences, first states the action and resource, second provides contextual use. No wasted words.

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 simple single-parameter read-only tool, the description provides the core function and a use case. It does not explain return values, but the absence of an output schema and the tool's simplicity make it reasonably 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?

The schema already provides 100% coverage of the 'category' parameter with examples and explanation. The description does not add further parameter-level details beyond referring to item classification.

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 retrieves item classifications from the Customs Tariff Law Annex (関税定率法別表の品目分類を取得します). It also specifies a particular use case related to catch-all regulations, distinguishing it from sibling tools that fetch other legal texts or parameters.

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?

It provides a specific context: used for checking items related to Article 16 of the catch-all regulation (キャッチオール規制の16項中欄). However, it does not explicitly mention alternatives or when not to use this tool, though the context implies its domain.

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