daily_training_briefing

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

The description discloses a mandatory external dependency and sequencing: it must call COROS_MCP_2 querySleepData for seven wake-up days and pass normalized results as officialSleepRecords. This goes beyond the readOnlyHint and destructiveHint annotations by explaining a required data-routing behavior.

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?

Two sentences carry the entire description with no filler, and the second sentence efficiently enumerates the data sources. The all-caps routing directive is front-loaded before the main purpose, which makes the structure serviceable but not ideal.

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?

The description gives a usable picture of the data flow and inputs, and annotations cover the safety profile. But with no output schema, it fails to state what the daily briefing returns, what output format to expect, or whether prior authentication is required, leaving important gaps for a complex aggregator.

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 schema documents date and the shape of officialSleepRecords fields, but the description adds that officialSleepRecords must be normalized results from querySleepData. However, 'normalized' is undefined, and the mandatory tone conflicts with officialSleepRecords being optional in the schema, so the added meaning is only partial.

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 states a concrete resource and action: build a daily briefing, and lists the data sources that feed it. It is distinguishable from a mere data fetch, though it does not explicitly differentiate itself from weekly_training_report or analyze_training_day.

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?

There is no explicit when-to-use guidance or mention of alternatives. The 'daily' and 'briefing' wording implies a daily cadence, but the description never says when to prefer this over sibling tools or when not to use it.

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