Cycle full report

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

Discloses support for cycle_irregular flag and includes a TL;DR string, but with no annotations, the description should cover permissions, side effects, or safety. It does not mention whether the tool is read-only or has any destructive actions.

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 conveying core purpose and a key feature. No superfluous text, though the version and feature hint could be integrated more smoothly.

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?

No output schema provided, and description only mentions a TL;DR string. For a composite report tool, the output structure (e.g., whether all sections are returned as strings) is missing, making it incomplete.

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?

With 0% schema coverage, description adds meaning only for cycle_irregular (PCOS-aware mode). Today and history parameters remain undocumented. Partial compensation, but insufficient for the other two parameters.

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?

Description clearly states verb (report) and resource (full report with phase, nutrition, training, hydration, next-period estimate). Distinguishes from sibling tools like cycle_estimate_phase or cycle_recommend_nutrition that cover individual components.

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?

Implies use when a comprehensive single-call report is needed, but does not explicitly state when to use versus alternative individual tools. No exclusion criteria provided.

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