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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds the dependency on a prior login and the account_link_id matching requirement, which is valuable behavioral context beyond annotations. It does not disclose pagination behavior or return format, but that is a minor gap given the annotation coverage.

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, efficient sentence that front-loads the critical login requirement before stating the purpose. There is no filler or redundant phrasing; every part earns its place.

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 read-only search tool with two self-documented parameters and no output schema, the description covers the essential purpose and the critical prerequisite. It does not detail what fields are returned, but the tool name and title convey the subject matter sufficiently, and the schema handles parameter semantics.

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 input schema provides 100% coverage of both parameters, including page_num's default and account_link_id's optional/resolution behavior. The description adds no parameter-specific 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?

The description states a clear verb-resource pair: 'Search assigned tax agent information.' The Korean title '나의세무대리인 조회' corroborates the purpose. While it doesn't explicitly differentiate from sibling search tools like hometax__tax__payment_statement__search, the specific resource 'assigned tax agent' is distinct enough.

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 gives a clear, actionable precondition: 'REQUIRES prior hometax__session__login call with same account_link_id.' This is strong contextual guidance for when the tool can be used. However, it does not mention alternatives or exclusions relative to other search tools.

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