get_preview_embed_dashboard_param_values

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

With no annotations, the description should disclose behavioral traits, but it only states the basic function. It does not specify whether the operation is read-only, requires authentication, or if it returns all values or just a subset. The description provides minimal behavioral context.

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, clear sentence with no unnecessary words. It is front-loaded with the action and resource, making it easy to parse quickly.

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 complexity (nested input object, many sibling tools), the description is insufficient. It does not explain the nested structure, the format of 'param_key', or the return values (no output schema). The tool's definition lacks completeness for effective agent use.

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?

Despite the context stating 0% schema description coverage (though 'token' has a description), the description adds no additional meaning to the parameters. 'param_key' lacks any schema description or explanation of expected format/values. The tool's description does not compensate for the sparse parameter documentation.

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 tool retrieves values for a parameter of a preview embedded dashboard in Metabase. It uses a specific verb ('Get') and resource ('parameter of a preview embedded dashboard'), distinguishing it from siblings like 'get_preview_embed_card_param_values' (card vs dashboard) and 'get_embed_dashboard_param_values' (non-preview).

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 like 'search_preview_embed_dashboard_param_values'. No prerequisites are mentioned (e.g., needing a valid preview embed token or a dashboard with parameters). The description lacks context for appropriate usage.

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