get_recovery_snapshot

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

With no annotations provided, the description carries the full burden of disclosing behavior. It does not state that the operation is read-only, describe the return format, mention permissions, rate limits, or any side effects. 'Fetch' implies reading but conveys no explicit behavioral traits, and the disclaimer is not behavioral.

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-loaded with purpose, using only two sentences. The 'Not medical advice' disclaimer is somewhat tangential but adds important context for health-related data, so it earns its place without being wordy.

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?

Given the tool's simplicity (one parameter, no output schema), the description covers the basic purpose but is incomplete for safe autonomous invocation. It lacks usage guidance, parameter explanation, and any behavioral context, making it minimally viable at best.

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 by explaining the 'day' parameter. The description does not mention the parameter at all, leaving the agent without information about how to specify day, format, or acceptable values beyond the schema's default.

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 clearly states the action ('Fetch') and the resource ('daily recovery and available performance context'), which conveys a specific purpose. However, it does not explicitly distinguish itself from sibling tools like get_daily_health or get_performance_metrics, so it falls short of a 5.

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 provides no guidance on when to use this tool versus the sibling tools, and there are no alternatives or exclusions mentioned. The only additional line is a disclaimer ('Not medical advice'), which does not help with usage decisions.

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