blog_competition

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

With no annotations, the description must carry the behavioral disclosure burden. It does state that it uses Naver Search API and specifies the returned data, which is useful. However, it does not mention potential caveats like API rate limits, authentication needs, ranking criteria for 'top' posts, or whether results are live vs cached.

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 with no filler. It front-loads the tool's main purpose and immediately follows with the return value details, making it easy for an agent to parse quickly.

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 single-parameter tool with no output schema, the description provides enough detail to call it correctly: input is keyword, output is total count plus top 10 posts with specified fields. It is slightly incomplete only because it does not define what 'top' means or mention any output format, but this does not block successful invocation.

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% with a single 'keyword' parameter already described as 'Keyword to search'. The description adds no additional parameter semantics beyond what the schema provides, which is acceptable given complete schema coverage.

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 uses a specific verb ('Analyze') with a clear resource ('blog competition for a keyword') and explicitly states the output: total post count and top 10 posts with metadata. It is clear enough to distinguish from siblings like search_volume or keyword_expand, though it does not explicitly name alternatives.

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 given on when to use this tool versus sibling tools such as niche_score, trend, or batch_analyze. The context implies keyword-level competitive analysis, but there are no explicit when-to-use or when-not-to-use instructions.

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