gitlab_get_user_activity_feed

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the return format in detail (event details, timestamps, project context, etc.) and mentions pagination via per_page and page parameters, which adds useful context. However, it does not cover critical aspects like authentication requirements, rate limits, error handling, or whether it's read-only/destructive, leaving gaps in transparency for a tool with 8 parameters.

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 well-structured with sections for purpose, returns, use cases, parameters, and an example, making it easy to scan. It is appropriately sized for an 8-parameter tool, but some parts (like the detailed return list) could be slightly condensed without losing clarity, keeping it from a perfect score.

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 the complexity (8 parameters, no annotations, no output schema), the description is moderately complete. It covers purpose, returns, use cases, and parameters adequately, but lacks details on authentication, error handling, rate limits, and exact output structure, which are important for a retrieval tool with filtering options. This leaves room for improvement in contextual coverage.

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 description coverage is 100%, so the baseline is 3. The description adds value by clarifying parameter usage: it explains that 'user_id or username' can be used interchangeably, provides an example with specific values, and lists all parameters with brief context. This enhances understanding beyond the schema, though it doesn't add deep semantic details like enum values or complex constraints.

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 specific action ('Retrieve user's complete activity/events timeline') and resource ('user activities including commits, issues, MRs, comments, and other interactions across all accessible projects'). It distinguishes from siblings like gitlab_list_user_events by emphasizing 'complete activity/events timeline' with detailed return structure, making the purpose specific and well-differentiated.

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?

The description provides clear use cases ('Track user engagement patterns', 'Monitor team member activities', etc.) that implicitly guide when to use this tool. However, it lacks explicit alternatives or exclusions, such as when to prefer gitlab_list_user_events or other sibling tools for simpler event listings, which prevents a perfect score.

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