sync_from_remote

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

With no annotations, the description carries the behavioral burden. It details days semantics (0, 7, 30), skipped local dates, failed-date reporting, and required S3 configuration. It does not explicitly state whether local files are overwritten or whether remote data is deleted, but the skipped-dates behavior implies a non-destructive sync.

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-structured with purpose, Args, Returns, Examples, and Note sections. Every section adds necessary information and the one-line purpose is 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 a tool with one parameter and an output schema, the description covers the return fields, the expected data flow, and configuration prerequisites. It is complete enough for an agent to select and invoke the tool correctly.

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 0% and the description fully compensates. The Args section explains days as '拉取最近 N 天' with default 7, enumerates special values 0/7/30, and the Examples section demonstrates invocation with and without arguments.

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 a specific verb and resource: '从远程存储拉取数据到本地' (pull data from remote storage to local). It clearly distinguishes this tool from siblings that check status or query data, and even states the MCP Server use case.

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 explains the intended context ('用于 MCP Server 等场景') and the data flow, giving clear context for when to use it. However, it does not explicitly mention when not to use it or name alternative tools.

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