get_activities

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the bar is lower. The description does add genuine behavioral context beyond the annotations: results are ordered newest-first and the call is paginated with defaults. It stops short of explaining page size limits or how to detect the end of the result set.

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 ordering and pagination fact is correctly front-loaded, but the second sentence ('Defaults `start=0, limit=20`.') is a verbatim restatement of the parenthetical in the first sentence. Roughly half the description is duplicated content that does not earn its place.

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 two-parameter list endpoint with no output schema, the description should at least hint at the page envelope (total count, whether more pages exist). It says 'a page' but never explains how an agent knows pagination is finished, leaving the caller to infer termination from an empty or short page.

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 carry the parameter burden. It supplies the defaults for both parameters (start=0, limit=20), which the schema does not, but gives no semantics for what start offsets from (an index? a timestamp?) or whether limit is capped.

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 states the resource (a page of activities) and an ordering trait (newest first), which tells an agent roughly what comes back. But it uses no verb and never distinguishes itself from the many siblings that also return activities (get_activities_by_date, get_activities_for_date, get_last_activity, get_activity, count_activities, get_gear_activities). An agent must guess which activity-listing tool is the unfiltered one.

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?

There is no when-to-use guidance at all: nothing says this is the unfiltered/paginated listing versus the date-scoped siblings. With ~140 sibling tools including several activity listers, the absence of any routing hint is a real gap, though the description is not actively misleading.

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