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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds the login prerequisite, which is useful behavioral context, but does not disclose other behaviors such as pagination limits, response format, or how optional parameters interact.

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 two short sentences, front-loaded with the critical prerequisite. It is efficient and avoids redundancy with the schema.

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 search tool with 9 parameters and no output schema, the description is minimal. It does not explain the distinction between submission date (sbms_ym) and taxation date (txtn_ym), nor does it clarify when to use the many optional filters. The login requirement is useful but not sufficient for full operational clarity.

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%, so the schema documents all parameters. The description explicitly mentions sbms_ym_strt and sbms_ym_end with YYYYMM format, but this is already in the schema. It does not add deeper meaning about optional parameters like txtn_ym_* or mate_knd_cd.

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 clearly states the tool searches tax declaration and payment submission history, which is a specific verb+resource. However, it does not explicitly differentiate from the sibling tool hometax__tax__payment_statement__search, which may have a similar purpose.

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 provides a prerequisite (prior login with same account_link_id) but does not mention when to use this tool versus alternatives like hometax__tax__payment_statement__search or other search tools. There is no guidance on conditions that would favor this tool.

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