trigger_crawl

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

Discloses that it triggers a crawl, returns JSON status with failed_platforms, and mentions optional saving to local directory. Without annotations, it covers key behavior but omits potential auth needs or rate limits.

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?

Well-structured with Args, Returns, and Examples sections, front-loading the main action. Slightly verbose but appropriate for a tool with multiple parameters.

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?

Given no annotations and output schema present, the description adequately covers the tool's behavior (inputs, returns, defaults). Could add more on error handling or performance, but sufficient for agent use.

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?

All three parameters are thoroughly explained: platforms with examples and default, save_to_local and include_url with their effects. This adds significant meaning beyond the schema which has 0% description coverage.

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 it triggers a crawl task with optional persistence, specifying the verb ('触发') and resource ('爬取任务'). It distinguishes from sibling tools that are analytical/retrieval, as no other tool performs crawling.

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?

Provides explicit examples and explains default behavior (using config.yaml platforms when not specified). Implicitly clear when to use (when a crawl is needed), but no explicit when-not or alternative sibling tool comparison.

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