get_my_activities

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

The description implies read-only behavior by saying 'Get', and mentions filtering. However, with no annotations provided, it doesn't explicitly state that the tool is non-destructive or safe, nor does it discuss pagination or authorization details beyond the implied logged-in user context.

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?

Single sentence conveying the tool's purpose and filtering ability without redundancy. Every word earns 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 filtered list tool with full schema coverage, the description is mostly complete. It covers the resource, scope, and filters. Minor gaps: no mention of default sort order or response structure (but no output schema needed).

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% with each parameter described. The description merely summarizes the filter capabilities, adding no new meaning beyond what the schema already provides.

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 verb 'Get', the specific resource 'the logged-in user's registered activities', and includes scope ('upcoming and past'). It effectively distinguishes from siblings like search_activities or get_member_activities by focusing on the user's own registrations.

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. For example, it doesn't contrast with search_activities for broader searches or get_member_activities for viewing others' activities.

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