zenn_search

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

With no annotations provided, the description carries the full burden. It states the tool uses an unofficial API, which is important for reliability awareness, but does not disclose other behavioral traits like rate limits, authentication needs, or potential data structure changes. The 'best for Japanese tech content' is vague and not actionable.

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 concise at three sentences, each adding value: platform, functionality, returns, usage context, and caveat. No redundant or extraneous content.

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 4 parameters, no output schema, and no annotations, the description provides adequate purpose and usage context. However, it lacks details on output structure (like topics, author info) and does not explain how the query parameter works as a topic slug + filter. May be sufficient for simple use but not comprehensive.

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 covers all parameters with 100% description coverage, explaining query as topic slug + keyword filter, article_type enum values, and order enum meanings. The description complements but does not add significant new info beyond the schema. Baseline 3 is elevated due to clear enum descriptions.

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 Zenn for technical articles using topic-based lookup with keyword filtering. It specifies the platform and content type, distinguishing it from other sibling search tools like qiita_search for Japanese tech content.

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 mentions it is best for Japanese tech content and notes the use of an unofficial API, providing some usage guidance. However, it does not explicitly advise when to use this tool over alternatives like qiita_search or other Japanese content sources.

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