get_dashboard_cards

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

The annotation readOnlyHint=true already discloses the safety profile. The description adds context about returning all cards and typical use cases, but it does not elaborate on return structure, pagination, or any further behavioral details. Given the annotation exists, this is acceptable but not exhaustive.

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, well-structured sentence that immediately states the core function and typical use cases. There is no redundant phrasing or filler.

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 has a single parameter with full schema coverage and an output schema that defines return values. The description sufficiently explains the tool's purpose and usage context for a straightforward read-only operation, so no additional details are needed.

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 describes dashboard_id as 'The ID of the dashboard' with 100% coverage. The description reinforces the concept of a specific dashboard but does not add additional meaning beyond the schema. Baseline of 3 applies.

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 action ('Retrieve') and the resource ('all cards within a specific Metabase dashboard'), distinguishing it from sibling tools like get_card (single card) or list_cards (potentially all cards). It also specifies the scope (specific dashboard) and intention (analyze content, understand data sources, examine configurations).

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 explicitly provides use cases ('use this to analyze dashboard content, understand data sources, or examine card configurations'), giving clear context for when to use the tool. It does not mention exclusions or alternative tools, but the context is sufficient for a simple read-only tool.

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