list_activities

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

No annotations provided; description carries full burden. It lists returned fields and mentions pagination, but does not explicitly state the operation is read-only or disclose any potential side effects. The absence of behavioral flags is acceptable for a list tool but could be improved.

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?

Three sentences that efficiently convey purpose, return fields, and key usage guidance without redundancy or unnecessary detail.

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?

Lists returned fields which is helpful given no output schema, but does not mention default ordering (e.g., most recent first) or behavior when no activities match. Sibling tools are distinct, so context is adequate but not fully complete.

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%, but the description adds valuable context: clarifies week_offset usage, calendar week definition (Monday-Sunday), and when limit is ignored. This enhances understanding beyond the schema descriptions alone.

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 succinctly states it lists activities with filtering and pagination and enumerates the returned fields. It does not explicitly differentiate from siblings like get_activity_detail, but the verb 'list' and field list imply this is the main listing tool.

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?

Provides explicit guidance on using week_offset for calendar weeks and explains parameter interactions (limit ignored when week_offset or both before/after are provided). Lacks explicit alternatives or when-not-to-use scenarios for sibling tools.

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