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

Annotations already cover read-only, idempotent, non-destructive semantics, so the bar is lower; the description still adds real value by explaining the 15,000-character paging behavior and by warning that an interpretation answers an individual question and is not binding like law. It omits any note on rate limits or what happens when an ID is not found, which keeps it short of a 5.

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 first sentence front-loads the verb, resource, and return contents; the ID provenance and paging rules follow in a logical order. The final clause about interpretations answering individual questions and not being binding is valuable but slightly crowds the sentence, so the text is dense rather than wasteful.

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 no output schema, the description properly compensates by listing the returned fields and explaining the paging of long documents. Combined with annotations covering the safety profile, an agent has nearly everything needed to call it, with only error and rate-limit behavior unaddressed.

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 coverage is 100% and both parameters are documented there, including the 18-digit ID / link format and the page minimum and default. The description only restates that the id comes from search results or a link and that pages are 15,000 characters, adding marginal meaning beyond the schema, so the baseline 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 verb and resource ('Get one Korean tax interpretation'), names the issuing authorities and the source system, and enumerates the returned parts (summary, body, related laws). It is clearly distinguishable from the sibling search_tax_interpretation, which produces the IDs this tool consumes.

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 tells the agent where the id comes from (search_tax_interpretation results or the original link), which gives a clear usage context. It does not, however, explain when to pick this over the similarly named get_interpretation or get_document siblings, so the routing is not fully closed.

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