get_morning_training_readiness

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

No annotations are provided, so the description carries the burden of conveying the operation. It clearly states this is a retrieval operation by saying 'Get' and 'Returns', which implies read-only behavior with no side effects. It also explains what the returned assessment evaluates, giving the agent useful behavioral context beyond the tool name.

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 compact, starts with the core purpose, adds one useful clarifying sentence about what the score evaluates, and includes the essential parameter format. There is no redundant or filler content; every line contributes to correct invocation.

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?

This is a simple one-parameter retrieval tool, and an output schema exists to define the return shape. The description covers the tool's purpose, the meaning of the score, and the exact date format. No critical information needed to call the tool correctly is missing.

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 compensate. It fully documents the single required parameter, 'date', and provides the crucial format constraint 'YYYY-MM-DD'. This goes beyond the schema's generic title 'Date' and gives the agent everything needed to supply a valid value.

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 uses a specific verb 'Get' with a specific resource 'morning training readiness score', and explains what the score represents: recovery status and readiness to train based on overnight metrics. The 'morning' qualifier and the reference to overnight metrics help distinguish this from sibling tools like get_training_readiness and get_training_status.

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 implies the tool is for retrieving the morning readiness assessment, and the overnight-metrics wording hints at when it is appropriate. However, it does not explicitly state when to prefer this over related tools such as get_training_readiness or get_body_battery, nor does it mention any exclusions.

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