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

With no annotations, the description must disclose behavioral traits. It only notes the output format ('English JSON'), but fails to mention any side effects, rate limits, required permissions, error behavior, or pagination. This is insufficient for an agent to safely invoke the tool.

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 extremely concise (one sentence) but at the cost of omitting essential details. While brevity is good, it should front-load key information like parameters and output structure. Here, it sacrifices completeness for brevity.

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?

Given the tool has three undocumented parameters, no output schema, and no annotations, the description is severely incomplete. An agent has no way to know what parameters to use, what values are valid, or what the response looks like. This makes the tool nearly unusable.

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 0%, yet the description adds no information about the three parameters (q, source, category). It does not explain their purpose, expected values, or how they affect the search. The agent must rely solely on the parameter names, which are ambiguous (e.g., 'source' could mean many things).

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 Korean products and lists example categories (K-beauty, K-food, K-pop merch). This distinguishes it from sibling tools that focus on building reports or getting financial data. However, it could be more precise about the scope (e.g., does it cover all Korean products or only those categories?).

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, expected use cases, or situations where another tool would be more appropriate. The agent is left to infer usage from the name and context.

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