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

Annotations already declare the full safety profile (readOnlyHint=false, destructiveHint=true, idempotentHint=false, openWorldHint=true). The description adds meaningful behavioral context beyond them: this is an asynchronous 'Builder task' submission with a fixed collector identifier. It still omits how results are retrieved and any auth/rate-limit context, so it is useful but incomplete.

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 heavy trigger-keyword preamble consumes most of the text before the actual purpose appears, and the 'Twitter 已更名为 X' note adds little for invocation. The operative sentence (the Builder task submission) is effectively buried, making the description keyword-stuffed rather than front-loaded.

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 an async task-submission tool with no output schema, the description should tell the agent the task is asynchronous and where results land (scraper_task_status / scraper_task_result). It stops at 'submit the task,' so a caller lacks the follow-through, even though the annotations cover the safety surface.

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 both parameters are already documented in the schema. The description only reiterates that a profile URL is used for the by-profileurl collector, adding no syntax, format, or constraint detail beyond what the schema provides. Baseline 3 applies.

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 states a specific action ('提交 Twitter(X) 帖子信息采集 Builder 任务') on a specific resource (Twitter posts) and gives the fixed collector identifier (twitter_post_by-profileurl). However, it never differentiates itself from the sibling twitter_profile, and the name/resource mismatch (a 'post' tool that ingests a profile URL) is only resolved by the collector id, so the purpose is clear but not sibling-differentiated.

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 lists trigger keywords (posts + collect/scrape/crawl/fetch/extract verbs), which gives implied usage intent and helps keyword routing. But it offers no explicit when-not guidance and does not point to alternatives such as twitter_profile or the scraper_task_* result tools, leaving the agent to infer the boundary.

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