get_metric_breakout_values

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

No annotations provided, so description must disclose behavior. It only says 'compute breakout values' without explaining what that entails, whether it requires an existing metric, or what the output format/likely is.

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?

Single short sentence with no unnecessary words. It's appropriately concise, though it sacrifices completeness.

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 one parameter with 0% schema coverage, no output schema, and no annotations, the description is severely incomplete. It fails to explain what the tool returns or any important usage constraints.

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%: the sole parameter 'definition' is an object with no property descriptions. The description adds 'MBQL metric definition' as a hint, but this is insufficient for a complex nested object. The agent lacks guidance on how to construct the MBQL definition.

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 ('compute') and resource ('breakout values for a metric definition'), distinguishing it from siblings like get_metric (which returns metric metadata) and get_metric_dataset (which returns a dataset). It could be more explicit about how it differs from search_metric_dimension_values or get_metric_dimension_remapping.

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_metric_dimension_values or search_metric_dimension_values. No prerequisites or context provided.

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