get_activity_splits

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about permissions, whether splits exist for all activity types (e.g., laps on non-interval activities), or pagination/size. Its field list duplicates the output schema rather than adding behavioral context, leaving the agent without key caveats.

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?

A single front-loaded sentence with the resource first and the returned metrics after; no filler or redundancy.

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 read tool with an output schema, the description is minimally sufficient to select and call it. However, with no annotations and no sibling differentiation, an agent cannot confidently decide between this and get_activity_detail without external knowledge.

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% and the single parameter activity_id has no description in the schema. The description's 'for one activity' obliquely clarifies the parameter's meaning and cardinality, but does not state the ID format or source (e.g., from get_recent_activities).

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?

Names a specific resource (per-lap splits for one activity) and enumerates what is returned (pace, HR, cadence, elevation, HR drift), so the agent knows exactly what data this yields. It does not distinguish itself from the likely-overlapping sibling get_activity_detail, leaving the agent to guess which to call for laps.

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 statement of when to use this versus get_activity_detail or get_recent_activities, and no prerequisites. The phrase 'for one activity' only weakly implies that a single activity_id is required, which the schema already enforces.

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