Get Activity Streams

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

With no annotations, the description must disclose behavioral traits on its own. It only states that the tool retrieves time-series data, which is evident from the verb, but does not address authentication, rate limits, pagination, units, or potential errors. Minimal additional transparency beyond the basic purpose.

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 a single, concise sentence that front-loads the main action and resource. Every word carries meaning, with no unnecessary filler. Well-structured for quick comprehension.

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?

The tool has no annotations, no output schema, and moderate complexity. The description provides a clear purpose and examples, but it lacks information about return format, how streamTypes affects output, or differentiation from sibling tools. It is adequate for a simple getter but leaves gaps that would benefit from expansion.

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?

The input schema already covers all parameters with 100% coverage, so a baseline of 3 is appropriate. The description adds marginal value by listing example stream types, but this is not essential since the streamTypes parameter description already provides examples. No significant new meaning is added.

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 clearly states a specific verb ('Ambil' = retrieve) and resource (time-series streams from a single activity). The examples (power, heart rate, cadence, altitude, distance, velocity) further clarify the scope, effectively distinguishing it from siblings like get_activity_details or get_activity_intervals.

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 description implies usage when you need stream data for a specific activity, but it does not explicitly mention when to use this tool over alternatives or provide any exclusion criteria. The guidance is purely implicit from the provided examples and tool name.

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