get_cardio_load

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

No annotations provided, so description carries full burden. It reveals output content but lacks disclosure on side effects, rate limits, or data freshness. Being a read operation is implied by 'Get' but not explicitly stated, and behavior when no date is given is only hinted as 'recent' without specifics.

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 succinct sentences with no redundant information. Every word adds value: defines the tool, explains its measurement, and lists the data fields returned.

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 one-parameter tool with no output schema, the description covers the main points: what the tool does, what data it returns, and parameter usage. However, it lacks explanations of output values (e.g., what constitutes acute vs chronic load) and error scenarios, leaving some gaps in completeness.

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 100%, baseline 3. Description adds value by clarifying the date format (YYYY-MM-DD) and the default behavior (returns recent data if not provided), which is not in the schema definition.

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 'Get' and resource 'cardio load data', and explains it shows acute load, chronic load, and load status. However, it does not explicitly distinguish from sibling tools like get_cardio_load_range or get_cardio_load_history, missing a chance to differentiate.

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 (get_cardio_load_range, get_cardio_load_history). The description implies usage for cardiovascular strain measurement but provides no explicit when-to-use or when-not-to-use criteria.

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