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 key behavioral traits: the tool returns CSDN search URLs rather than actual content, and requires follow-up with WebFetch tool to get results. This is valuable context beyond what the input schema provides about the tool's operational behavior.

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 efficiently structured with an emoji icon, clear title, and two focused sentences. The first states the purpose, the second provides critical implementation guidance. Every element earns its place with no wasted words.

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 with URL return pattern), no annotations, no output schema, and 0% schema description coverage, the description is partially complete. It explains the URL return behavior well but lacks parameter documentation and doesn't describe what the returned URLs contain or how to interpret them.

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 for 2 parameters (query and type), the description provides no information about parameter meanings, formats, or usage. The schema alone shows query is required and type is optional, but the description adds no semantic context about what these parameters represent or how they affect the search.

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 CSDN for technical blogs and Q&A, providing a specific verb ('搜索') and resource ('CSDN技术博客和问答'). It distinguishes from siblings by specifying the CSDN platform, though it doesn't explicitly contrast with other search tools like ai_search_github or ai_search_stackoverflow.

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 implies usage when searching CSDN content, but doesn't provide explicit guidance on when to use this tool versus alternatives like ai_search_github or ai_search_stackoverflow. The second sentence provides important implementation guidance but not comparative usage context.

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