get_recent_activities

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

With no annotations, description bears full burden. It only states return content (list of workouts with basic info) but does not disclose ordering, pagination behavior, rate limits, or that the tool is read-only. For example, it doesn't specify default sort order (likely most recent first) or what 'recent' means in absence of date filters.

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?

Description is two sentences, front-loaded with the main action, no filler. Every word serves a purpose: states what it gets and what it returns. Efficient and to the point.

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?

Given 4 optional parameters and no output schema, the description is insufficient. It doesn't explain default behavior for limit, meaning of 'recent', ordering of results, or any constraints. The agent lacks enough context to fully understand the tool's behavior without additional schema reading.

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 100% as every parameter has a description. The tool description adds no extra meaning beyond the schema; it does not elaborate on parameters like limit or toDate. Baseline score of 3 is appropriate since schema already documents parameters.

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?

Description clearly states 'Get recent Coros activities' with specific verb and resource, and mentions return of basic info like date, name, sport type. This distinguishes it from siblings like get_activity_details (likely full details) and get_activity_file_url (specific file). The purpose is unambiguous.

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 vs alternatives. It does not mention that for full activity details one should use get_activity_details, or for file URLs use get_activity_file_url. Context for tool selection is missing.

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