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

With no annotations, the description carries the full burden. It discloses meaningful behavior: it validates the 統一編號 checksum and pulls data from the 經濟部 (Ministry of Economic Affairs) registry, and it lists the fields returned. It does not, however, state read-only/auth/rate-limit behavior or failure modes.

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?

A single compact sentence that front-loads the verb and resource and then lists outputs; essentially no waste. It stops short of five only because it packs no usage or parameter disambiguation into that brevity.

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 lookup tool with no output schema and no annotations, it covers the return side reasonably by naming the returned fields, but leaves the input side under-specified: two 0%-documented parameters and no explanation of how ban and name relate.

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 description coverage is 0%, so the description must compensate and largely does not. It implies the tax-ID parameter via the checksum mention (ban/統一編號), but says nothing about the 'name' parameter, whether the two are alternatives, or that both are optional.

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?

States a specific verb (查/look up) and resource (台灣公司 Taiwan companies), and enumerates the concrete outputs: tax-ID checksum verification plus Ministry of Economic Affairs registration status, representative, capital, and address. It is clear on its own, but does not differentiate from siblings such as check_tax_registration, which overlaps on tax-ID territory.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of the similarly scoped sibling check_tax_registration. An agent must infer the usage context (supplier/company validation) purely from the name and description.

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