Get menstrual cycle

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

The annotations already establish that this is a read-only, open-world operation. The description adds meaningful behavioral context by listing the returned fields, including pregnancy details when tracking a pregnancy, which is important because there is no output schema.

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 and front-loaded: it starts with the core summary purpose, lists relevant returned fields, then documents the date parameter. It does not waste space on irrelevant detail.

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 read-only getter with no output schema, the description provides enough output context for an agent to know what will be returned. It is slightly incomplete because it does not clarify sibling selection or how missing/no-tracking data is handled.

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 carry parameter meaning. It does so for the single optional date parameter by specifying the YYYY-MM-DD format and defaulting to today.

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 that this returns a menstrual cycle summary as of a date and enumerates the key fields returned. It is specific about the resource and scope, but it does not explicitly distinguish itself from the sibling garmin_get_menstrual_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?

It implies usage by saying the summary is as of a date and that the date defaults to today. However, it gives no explicit guidance on when to use this tool versus garmin_get_menstrual_day or other wellness getters.

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