calendar_sync_background

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

No annotations are provided, so the description carries the full burden, and it delivers real operational detail: it pushes local create/update/delete/respond changes and pulls server changes, and runs headless with the screen off. It omits failure behavior, network requirements, and whether partial failures roll back, so it is strong but not complete.

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 key scope and mechanism are front-loaded and the total is three sentences with no filler. The closing sentence about calendar_sync falling back to the app is slightly compressed and takes a moment to parse, which keeps it from a 5.

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 two-optional-parameter sync tool with no annotations and no output schema, the description covers what is synced, in which direction, and under what device conditions. Return values and error semantics are absent, but the essentials for a correct invocation are there.

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 100% and both parameters (wait, timeout) have their own descriptions, so the schema does the semantic work. The description adds no parameter-level detail, making the baseline 3 correct.

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?

States a specific verb and resource ("Sync the calendar with Google") plus the mechanism (Android sync manager, requestsync) and scope (without the screen). It explicitly distinguishes itself from the closest sibling calendar_sync, so an agent can pick between them without opening a schema.

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?

Gives a concrete usage condition (works with phone locked and screen off) and names the alternative (calendar_sync) with its distinguishing fallback behavior. It never states an explicit when-not-to-use case, which keeps it short of a 5, but the context needed to choose is present.

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