list_taxes

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

No annotations exist, so the description carries the behavioral burden. '取得' and '一覧' convey read-only list retrieval, which is a basic behavioral trait. However, the description does not mention response structure, pagination, or scope beyond the schema, so transparency is adequate but minimal.

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 one short, focused sentence with no filler. It front-loads the resource and action and is appropriately sized for a simple list tool.

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 one-parameter list tool, the description identifies the purpose and the schema covers the required parameter. However, with no output schema or annotations, the return structure and broader usage context remain unspecified, leaving a moderate completeness gap.

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 single parameter company_id is fully documented in the schema with type and description (事業所ID), giving 100% schema coverage. The description adds no parameter-level meaning beyond what the schema already provides, so the baseline score of 3 applies.

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?

Description is '税区分コード一覧を取得' — a specific verb (取得) and resource (税区分コード一覧). It unambiguously identifies a list of tax classification codes and is distinguishable from all sibling tools, none of which target tax codes.

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?

No explicit when-to-use or alternative guidance is given. The usage is implied: this tool should be used when a list of tax classification codes is needed. Since there is no direct sibling overlap, the lack of exclusions is not critical, but the guidance is still only implicit.

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