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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only and dynamic-world behavior is covered. The description adds useful behavioral context beyond annotations by stating that pagination is supported, and the detailed page_token handling rules further clarify expected usage. No contradiction exists.

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 compact: three sentences, each earning its place. The primary action is front-loaded, usage guidance follows, and pagination is mentioned last without any verbose filler.

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 read-only search tool with an output schema, annotations, and detailed parameter schemas, the description is fully adequate. It tells the agent what the tool does, when to use it, when to use alternatives, and that pagination is available, leaving no critical gap.

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 description coverage is 100%, so the schema fully documents both parameters. The main description adds no new parameter-level meaning beyond saying pagination is supported; the keyword and page_token nuances are already captured 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 opens with '按搜索词搜索微博帖子' (search Weibo posts by search term), a specific verb and resource. It then explicitly contrasts itself with post-specific and user-specific tools, so an agent can distinguish it from the many sibling tools.

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?

It states plainly to use this tool when the user wants to find posts by keyword or phrase, and gives explicit exclusion conditions: use the corresponding post tools when a post link or post_id is available, and user tools when a profile link or user_id is available. It also mentions pagination support with page_token.

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