smart-search

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

With no annotations provided, the description carries full burden. It discloses the key behavioral trait that the tool returns URLs rather than actual search results, which is crucial information. However, it doesn't mention rate limits, authentication requirements, pagination behavior, or error handling that would be helpful for a search 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 with only two sentences, both of which earn their place. The first establishes purpose, the second provides critical usage guidance. The emoji and formatting (【重要】) help with visual structure without adding unnecessary 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's moderate complexity (search functionality with 2 parameters), no annotations, no output schema, and 0% schema coverage, the description is incomplete. While it covers the crucial behavioral aspect (returns URLs), it lacks parameter documentation and doesn't explain what the output looks like beyond 'URLs'. The WebFetch guidance helps but doesn't fully compensate for missing documentation.

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?

With 0% schema description coverage and 2 parameters (query and sort), the description provides no information about parameter semantics. It doesn't explain what the query parameter expects, what the sort parameter does, or what sorting options are available. The description fails to compensate for the complete lack of schema documentation.

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 for articles on the Juejin technical community platform ('搜索掘金技术社区文章'), which is a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like ai_search_csdn or ai_search_segmentfault that also search Chinese tech communities, missing full sibling differentiation.

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 explicit usage guidance with the 【重要】 section stating '此工具会返回掘金搜索URL，Claude Code应该使用WebFetch工具访问该URL以获取真实搜索结果' - this clearly indicates when to use this tool (to get search URLs) and what alternative tool to use next (WebFetch for actual results), creating a complete workflow context.

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