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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral context by requiring a prior hometax session login and tying it to account_link_id. It does not mention return format or pagination behavior, but the auth requirement is meaningful beyond the 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?

Two sentences with no filler. The prerequisite is front-loaded, and the second sentence efficiently maps the core parameters. Every word 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?

The required prerequisites and core parameters are covered, and the schema handles the rest of the parameter details. However, with no output schema and no description of what the search returns or how pagination behaves, the description is slightly incomplete for an agent trying to use the result correctly.

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 schema already documents all seven parameters, including formats and defaults. The description's mention of 'bsno', 'stl_yr', and 'qrt_from/qrt_to' reinforces which parameters matter, but adds no meaning beyond what the schema already provides.

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 specific verb and resource: 'Search credit card sales data' with business number, year, and quarter parameters. It is clearly distinguishable from most siblings by the 'credit card' scope, though it does not explicitly name an alternative or contrast with similar hometax search tools.

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 states a required precondition: prior hometax__session__login with the same account_link_id. This is strong usage guidance for an authenticated data-lookup tool, but it does not explicitly say when to prefer this tool over alternatives or when not to use it.

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