get_activity_streams

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

With no annotations, the description carries the burden of behavioral disclosure. It states that streams are returned and documents the default stream keys when keys is null, but it does not discuss units, missing stream behavior, pagination, or side effects beyond the implied read-only nature of 'Return.'

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, with a clear one-line purpose statement followed by a succinct parameter list. No filler or redundant restatement of the schema appears.

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 low-complexity read tool with no output schema and no annotations, the description covers the required parameter, optional key selection, defaults, and return concept. It does not specify response shape or units, but the essential invocation information is present.

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 compensate. It fully explains both parameters: activity_id is 'the activity to inspect,' and keys lists the stream types to fetch with a concrete default set. This is exactly the semantic information an agent needs beyond the raw schema.

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 opens with a specific verb and resource: 'Return time-series streams for an activity.' It further narrows the purpose with 'for detailed pace/HR/elevation analysis,' which clearly distinguishes it from siblings like get_activity, get_stats, and list_activities.

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?

The phrase 'for detailed pace/HR/elevation analysis' implies when to use the tool, but the description does not explicitly say when to prefer it over get_activity or get_stats, nor does it mention exclusions or alternatives.

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