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 covered. The description goes well beyond annotations by explaining the meaning of totalCount (record count, never fewer than rows), the collectionMeta flag (complete vs collectedCount), and explicitly instructing pagination when complete is false. This is rich behavioral disclosure well beyond annotations.

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 a single paragraph but dense and front-loaded with the most critical requirement (login) and scope (single day). It uses compact sentences and avoids fluff, though the count explanations could be tightened. Still, every sentence adds value, so it earns a four rather than a five.

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 compensates by explaining the return fields (totalCount, collectionMeta, collectedCount) and pagination logic. It covers login, date scope, and parameter nuances. An agent has everything needed to call this correctly and interpret results. Highly complete.

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%, so the baseline is 3. However, the description adds practical context for parameters: trs_dt defaults to today, account_link_id should be explicit only with multiple certificates, and the pagination instruction ties page_num to the collectionMeta.complete flag. This goes beyond the schema's field-level descriptions and aids correct invocation.

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 opening sentence states a specific verb and resource: 'Search cash receipt issuance records for a single day (당일 발급 조회)'. This clearly distinguishes it from sibling tools like purchase search and sales search, and the same-day scope is explicit. Purpose is 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 explicitly requires a prior hometax__session__login call with the same account_link_id, and states that the endpoint is same-day only, so other dates are not supported. It does not name alternatives explicitly, but the same-day restriction and login prerequisite are clear and actionable usage guidance.

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