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 search URLs rather than actual content, and Claude Code should use WebFetch to access those URLs. This is valuable context about the tool's output format and required follow-up actions, though it doesn't cover rate limits, authentication needs, or error handling.

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 efficient with two sentences: one stating the purpose and scope, and another providing crucial behavioral information. Every element earns its place, and the important implementation note is appropriately highlighted.

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 search tool with no annotations, no output schema, and 2 undocumented parameters, the description provides adequate purpose and behavioral context but leaves significant gaps. It explains what the tool does and how to use its output, but doesn't address parameter meanings, result formats, or error conditions that would be needed for complete understanding.

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, the description provides no information about what 'query' or 'platform' parameters mean, their formats, or valid values. The description doesn't compensate for the complete lack of parameter documentation in the schema.

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 WeChat developer documentation for mini-programs, public accounts, and open platform docs. It specifies the resource (WeChat docs) and verb (search), but doesn't explicitly differentiate from sibling tools like ai_search_tencent_docs or ai_search_docs beyond mentioning WeChat specifically.

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 context by specifying WeChat documentation search, but doesn't provide explicit guidance on when to use this tool versus alternatives like ai_search_tencent_docs or ai_search_docs. The important note about using WebFetch for actual results provides implementation guidance rather than selection guidance.

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