taiwan_company_verify

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

No annotations are provided, so the description carries the full burden. It discloses the data source (MOEA OpenAPI) and notes it is 'real-time', but does not discuss rate limits, authentication, error handling, or potential side effects. It is adequate but lacks depth for a comprehensive understanding.

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 two sentences, front-loaded with the core purpose, and every sentence adds necessary information without redundancy. It is appropriately concise.

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 tool has only one parameter, no output schema, and several similar siblings, the description is sufficiently complete to understand what the tool does and how to use it. It covers data source, use case, and parameter format.

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 has 100% schema coverage, and the description adds a clear example ('例如 22099131') and specifies the length (8 digits). This adds value beyond the schema, aiding correct usage.

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 it uses an 8-digit unified business number to fetch real-time official registration status from the MOEA's OpenAPI, listing specific fields (name, status, capital, etc.). It distinguishes itself from databases by being more real-time, making the purpose specific and unambiguous.

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 usage context (checking if a company is still existing or dissolved) but does not explicitly state when not to use it or compare with sibling tools like taiwan_company_profile or taiwan_company_search. Usage guidance is implied but not fully explicit.

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