get_dashboard_param_values

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

No annotations provided, so the description must disclose behavior. It only says 'Get possible values' without mentioning auth requirements, error handling, or whether the operation is idempotent. The description is minimally informative about 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 a single sentence, which is concise, but it lacks structured details. It is neither overly verbose nor efficiently packed with necessary information.

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 absence of output schema, annotations, and the presence of multiple sibling tools, the description is insufficient. It does not specify return format, pagination, or any constraints, leaving the agent with incomplete context to use 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 description coverage is 0%, meaning the description is the only source. It adds the phrase 'dashboard filter parameter' but does not explain the parameters beyond their names and types. The 'id' and 'param_key' have bare descriptions in the schema, but the description adds no additional semantics.

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 'Get possible values for a dashboard filter parameter in Metabase', using a specific verb and resource. It distinguishes from sibling tools like get_card_param_values or get_embed_dashboard_param_values by focusing on dashboard parameters.

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?

No guidance on when to use this tool versus alternatives such as get_card_param_values, get_embed_dashboard_param_values, or search_dashboard_param_values. The description lacks context on prerequisites or conditions.

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