icu_get_athlete_profile

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

No annotations are present, so the description must carry behavioral disclosure. It conveys a read-only retrieval operation with env-based auth fallback, but doesn't explicitly state side-effect-free behavior, error/rate-limit behavior, or response format (though output schema covers return shape).

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?

Front-loaded summary line followed by concise, useful parameter docs. No redundant or filler content.

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 simple two-optional-param getter with an output schema, the description covers the essential invocation details. It could add sibling differentiation, but that gap is already captured under usage guidelines.

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 coverage is 0%, but the Args section documents both parameters and adds fallback semantics (ATHLETE_ID/API_KEY from env). This meaningfully compensates for the bare schema, though it doesn't specify value formats beyond the schema's string type.

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?

Clearly states a specific verb ('Get'), resource ('athlete profile, FTP settings, LTHR, weight, and power/HR zones'), and source ('Intervals.icu'). This distinguishes it from sibling getters like get_athlete_power_curves and get_wellness_data.

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?

No guidance on when to use this tool versus alternatives such as get_athlete_power_curves or get_activity_details. It only mentions optional args and env fallback, not selection criteria or exclusions.

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