preview_daily_adjustment

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's 'Never change the calendar' reinforces but does not contradict them. The mandatory sleep-routing precondition adds useful behavioral context beyond the annotations by telling the agent what must happen before this preview can be called.

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 short and front-loads the most operationally important instruction. Every clause earns its place, though the all-caps 'MANDATORY' is unnecessary noise and the final 'Then preview the daily adjustment' mostly restates the tool name.

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?

With no output schema, the description must explain what the agent can expect from the preview and what inputs it truly needs; it does neither. Terms like 'required recent wake-up days' and 'normalized results' are undefined, and the purpose of a 'daily adjustment' is never explained. The safety profile is covered by annotations, but call correctness is not.

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?

The date parameter is the only one described in the schema, while officialSleepRecords and its many nested fields are not. The description does add some meaning by explaining that officialSleepRecords should be normalized results from querySleepData, but it does not specify field mapping, required recency, or normalization rules. It partially compensates for the 50% schema coverage but leaves significant gaps.

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 says 'preview the daily adjustment,' which is close to a tautology with the tool name and never defines what a daily adjustment is or what previewing it entails. The lengthy mandatory-routing preamble obscures the core purpose instead of clarifying it. There is no differentiation from sibling planning or summary tools.

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 gives explicit sequencing: first call COROS_MCP_2 querySleepData, pass normalized results as officialSleepRecords, then preview. It also adds a clear boundary with 'Never change the calendar.' What it lacks is any guidance on when this tool should be chosen over sibling tools or when it should not be used.

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