superset_recent_activity

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

No annotations are provided, so the description must disclose behavior. It explains pagination semantics, including that get_all overrides page/page_size and automatically paginates. It also scopes activity to the current user and lists activity types (views, edits). However, it does not mention authentication requirements, whether the operation is read-only (though implied), or any other side effects or limitations.

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 succinct and well-structured. It starts with a clear one-sentence purpose, then lists each parameter with its behavior. There is no wasted wording, and all sentences contribute to understanding the tool.

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 tool's low complexity and the presence of an output schema, the description is largely complete. It explains all parameters and their interactions. Minor gaps include not specifying whether the activity list can include other types beyond views and edits, and not mentioning any date filters or sorting behavior. Still, it provides enough for an agent to invoke the tool correctly.

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 0%, so the description fully carries parameter semantics. It explains page starts at 0, page_size max is 100, and get_all fetches all records with automatic pagination, ignoring page/page_size. This adds meaningful usage guidance beyond the bare schema, which only shows defaults.

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 tool gets recent activity of the current user, specifically views and edits. It uses a specific verb and resource, making the purpose understandable. However, it does not explicitly distinguish itself from sibling tools like superset_log_list or superset_get_current_user, though the 'current user activity' scoping helps.

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 no guidance on when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or preferred contexts. For example, there is no note that this should be used over superset_log_list for user-centric activity tracking. The only usage-related details are parameter explanations, not scenario-based guidance.

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