get_measure_dimension_values

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

With no annotations, the description must disclose behavior. It only states 'Fetch values,' but does not indicate whether the operation is read-only, requires permissions, has side effects, or details about pagination or response format.

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 concise at one sentence with no unnecessary words. However, it is too brief and could be expanded to include key usage information without sacrificing conciseness.

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 tool with a nested input object, two required parameters, no output schema, and no annotations, the description is insufficient. It does not clarify how to use the parameters, what the return values look like, or how it relates to sibling tools.

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 input schema has descriptions for both parameters ('Measure ID' and 'Dimension key of the measure'), but the description adds no additional meaning. Given the schema description coverage is 0% (per context), the description fails to compensate by explaining what a 'dimension key' is or how to obtain it.

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 uses the verb 'Fetch' and identifies the resource as 'values for a dimension of a measure' in Metabase, which is clear. However, it does not distinguish this tool from siblings like get_metric_dimension_values or search_measure_dimension_values, which have similar purposes.

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 is provided on when to use this tool versus alternatives such as search_measure_dimension_values or get_measure_dimension_remapping. There is no mention of prerequisites, use cases, or exclusions.

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