list_activities

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

With no annotations provided, the description carries full burden. It mentions 'cached' and 'units fixed', giving some behavioral insight, but fails to disclose other traits like read-only nature, rate limits, or response behavior for missing data. Significant gaps remain.

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, front-loading the core action and key features. While efficient, it could include more detail without sacrificing brevity, but it earns a high score for avoiding verbosity.

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?

Despite having an output schema and 5 parameters, the description does not mention sport_type filtering or explain the caching behavior's impact. It also uses 'rides' instead of 'activities', potentially confusing. The description is incomplete for a list tool with filtering and paging.

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 0%, so description must compensate. It explains date range (start_date, end_date) and paging (limit, offset) as optional, but omits the sport_type parameter entirely. This partial coverage provides basic meaning but leaves one parameter undocumented.

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 the tool lists rides (activities) with optional date range and paging. It uses a specific verb 'List' and resource 'rides', which is distinct from sibling tools like get_activity_summary or compare_activities, though the term 'rides' slightly diverges from the tool name '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?

No guidance on when to use this tool versus alternatives such as get_activity_summary or compare_activities. The description lacks any 'when to use' or 'when not to use' information, leaving the agent without context for selection.

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