search_articles

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

No annotations are provided, and the description does not disclose key behaviors like whether results are paginated, sorted by relevance, or what 'smart filtering' actually does. The phrase '智能过滤' is vague and does not help predict the tool's output format or side effects.

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 a single short sentence that immediately states the core function. It is front-loaded and contains no filler words or redundant information.

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?

With three parameters and no output schema or annotations, the description is under-specified. It does not explain what 'smart filtering' entails, what the response structure looks like, or any caveats like rate limits or authentication requirements, leaving the agent without enough context to use the tool safely and effectively.

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 describes all three parameters (keyword, limit, include_analysis) with Chinese descriptions, giving 100% coverage. The tool description adds the notion of 'smart filtering' but does not clarify how parameters like include_analysis relate to it, so it adds marginal value beyond 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 Juejin articles and supports keyword search and intelligent filtering. It uses a specific verb and resource, and the keyword/search concept distinguishes it from general listing tools like get_articles, 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?

There is no guidance on when to use this tool versus alternatives such as get_articles, search_pins, or get_trending_articles. The description only states capabilities, not when to choose this tool.

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