get_user_activity_history

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

With no annotations, the description carries the full behavioral disclosure burden. It does not state whether the activity is for the current user or a specified user, what the response items look like, how pagination works, or whether any side effects or auth requirements apply. The examples of activity types are helpful but under-specified.

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?

Two short sentences with no filler; the main action and examples come first and the filter capability second. It earns its place, though the second sentence could be more precise about which parameters map to 'activity type and project.'

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?

The tool has seven parameters, no annotations, and no output schema, yet the description does not cover the user-scope ambiguity (current user vs specified accountId/username) or the return shape. For an activity-history tool, the agent needs to know what a result entry looks like and how the identity of the user is determined, so the description is incomplete.

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%, so the schema already documents all seven parameters. The description adds a little value by clustering 'activity type and project' as filters, but it does not explain the relationship between username and accountId or the default user scope, so it stays at baseline.

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 names a specific verb ('Get'), resource ('stream of recent user activity'), and gives concrete examples (issue comments, status changes, field updates). It is clear on its face but does not distinguish itself from sibling tools like get_user_time_tracking or get_my_recent_confluence_pages.

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 is provided about when to use this tool instead of the many related siblings (e.g., search_issues_by_user_involvement, get_user_time_tracking). There is no 'use this when...' or 'use X instead for...' instruction, leaving the selection entirely to inference.

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