list_dashboards

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

The description aligns with the readOnlyHint annotation via the verb 'Retrieve'. It adds no additional behavioral details such as pagination, ordering, or limiting, and with an output schema present, the return structure is already defined. The added value beyond annotations is minimal.

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 a single, front-loaded sentence that states the primary action clearly and then lists use cases. No filler or redundant words beyond the slight overlap between 'Retrieve all dashboards' and 'discover available dashboards'.

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?

For a zero-parameter read-only list endpoint with an output schema, the description fully covers the purpose and gives practical usage scenarios. There is no missing critical information such as required inputs or side effects.

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 tool has no parameters, and the schema coverage is effectively 100% (empty schema). There are no parameter semantics to explain, so the baseline for zero-parameter tools applies (4). The description correctly omits parameter details.

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 begins with 'Retrieve all Metabase dashboards', a specific verb and resource. The word 'all' clearly distinguishes this from sibling tools like get_dashboard (single dashboard) or get_card_dashboards (dashboards related to a card).

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?

It provides clear usage context: 'use this to discover available dashboards, get an overview of analytical content, or find specific dashboards'. It does not explicitly mention alternatives or when not to use it, but the context is sufficient for a simple list tool.

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