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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds crucial behavioral context beyond the annotations by mandating a prior login and requiring the same account_link_id, which is material for correct invocation. It relies on the schema for format details, which is acceptable.

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, each carrying essential information: the prerequisite warning and the core purpose. The most critical constraint (login requirement) is front-loaded, and there is no redundant or filler content.

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 only two parameters, no output schema, and annotations covering safety, the description provides the essential context: a mandatory prerequisite and the search-by-number semantics. It does not describe the response payload, but for a read-only status lookup the core agent needs is present.

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 100% and both parameters are already well documented, including the optional account_link_id behavior and automatic hyphen stripping for txpr_dscm_no. The description's mention of 'same account_link_id' reinforces the schema but does not add new semantic information, so the baseline 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?

States a specific action ('Search business registration status') and a precise resource ('business registration number'), which cleanly identifies what the tool does. The Korean title reinforces the same concept确, and the scope is unambiguous even though the description doesn't explicitly distinguish from the sibling hometax__tax__business_registration__search_info.

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?

Explicitly requires a prior hometax__session__login call with the same account_link_id, giving a concrete precondition and tying the account_link_id parameter to the session. It does not mention when to prefer this over the similarly named search_info sibling, but the login prerequisite and the search-by-number instruction clearly frame the intended context.

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