superset_dashboard_list

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

With no annotations, the description carries the disclosure burden. It reveals pagination behavior, the max page size (100), and get_all's effect of ignoring page/page_size. It does not detail return formats or authentication, but the output schema covers return structure, so this is a strong disclosure of behavioral traits.

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: the core purpose is stated first, followed by a critical usage note, then parameter definitions. The RISON examples are lengthy but directly useful for constructing filters, and every sentence adds necessary value.

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 is a listing endpoint with pagination and filtering; the description covers all operational aspects: pagination, max page size, filter syntax, and get_all behavior. It also provides a workflow hint (call before dashboard_get) that makes it complete for an agent to use 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 has 0% description coverage, but the description fully explains each parameter: page (starting from 0), page_size max 100, q with concrete RISON examples for title/owner/published filters, and get_all's automatic pagination. This fully compensates for the lack of param descriptions in the schema.

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 lists Superset dashboards with pagination, using a specific verb and resource. It explicitly distinguishes itself from dashboard_get by instructing users to call this first to discover dashboard IDs.

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?

Provides explicit usage guidance: 'always call this tool before dashboard_get' and explains pagination parameters, filtering options, and the get_all behavior. This tells the agent when to use it and how to use it effectively.

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