weibo_search

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

With no annotations provided, the description fully discloses behavioral traits: it uses m.weibo.cn mobile API, parses cards[].mblog, requires a specific cookie file, and is concurrency-safe. This adds significant value beyond the schema.

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 with multiple bullet points covering purpose, prerequisite, principle, and safety. It is front-loaded and efficient, though could be slightly more structured for readability.

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?

The description covers prerequisites, underlying API, cookie handling, and concurrency. It also references an alternative sibling tool. With an output schema present (as indicated by context), the missing return value details are acceptable. Still, the description is fairly 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?

Schema coverage is 100%, and the schema already describes both parameters (keyword, limit) adequately. The description does not add additional parameter-specific information beyond the schema, so it meets the baseline for schema-rich tools.

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 explicitly states '搜索微博帖子' (search Weibo posts), clearly identifying the action and resource. It also mentions the need for login and distinguishes from weibo_hot_list, which does not require login, aiding differentiation among siblings.

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 guidelines: requires login cookies (SUB token), guest mode not available, and an alternative (weibo_hot_list) that does not need login. It also notes concurrency safety and cookie file location, giving clear when-to-use and when-not-to-use context.

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