superset_log_list

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It adds valuable context beyond a simple 'Get' by explaining pagination semantics, the 'get_all' automatic-pagination behavior, and filter syntax with concrete examples. It does not mention permissions, rate limits, or side effects, but for a read-only list operation this is fairly transparent.

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: a one-sentence purpose clearly front-loaded, followed by a compact list of arguments and examples. Every sentence provides necessary information—no fluff or repetition.

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?

With an output schema present and all four parameters thoroughly documented, the description is largely complete. The only notable gaps are the absence of explicit differentiation from similar audit/recent-activity tools and lack of operational details like rate limits or error handling, but these are not critical for basic usage.

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?

The schema description coverage is 0%, so the description must fully explain the parameters. It does so comprehensively: page (start at 0), page_size (max 100), q (with two examples), and get_all (ignores page/page_size). This adds meaning far beyond the bare schema properties and 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 opens with 'Get the audit log of all Superset user actions', which is a specific verb+resource combination. It clearly identifies the tool's function, but it does not explicitly differentiate this from siblings like 'superset_permissions_audit' or 'superset_recent_activity', so it stops short of full distinction.

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 detailed parameter usage and examples (e.g., RISON filters for user/action), which implies when to use the tool for audit log queries. However, there is no explicit guidance on when to prefer this over alternative tools, nor any exclusions or preconditions.

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