sync_from_remote

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

No annotations are present, so the description carries the full burden. It explains the days=0/7/30 semantics, skipped local dates, the complete return shape, and required S3 configuration. This gives the agent a strong behavioral model.

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 well-organized into purpose, Args, Returns, Examples, and Note sections. Every section adds necessary information, and the structure makes it easy for an agent to parse.

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 single-parameter tool, it provides everything needed to call it correctly: behavior, parameter choices, result format, and configuration prerequisites. Even with an output schema present, the practical context is valuable.

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 0%, so the description must define the parameter. It thoroughly documents 'days' with default, special values, and examples, far exceeding the bare integer 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 begins with a specific verb and resource: '从远程存储拉取数据到本地' (pull data from remote storage to local), and explains the MCP Server scenario. This clearly distinguishes it from siblings like trigger_crawl or list_available_dates.

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 gives a concrete use case: crawlers upload to remote cloud storage and the MCP Server pulls data locally for analysis. It does not explicitly name alternatives or state when not to use this tool, so it does not achieve the top score.

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