preview_embed_dashboard

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

Without annotations, the description carries the full burden. It only discloses the 'admin only' constraint but omits other behavioral traits such as what the preview returns (e.g., dashboard view, data), whether it requires authentication beyond admin status, or if it has any side effects. The description is insufficient for an agent to understand the tool's full behavior.

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 and front-loaded with the key verb. However, it may be too short, sacrificing necessary detail. Every word earns its place, but the brevity hinders 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 the lack of output schema and the complexity of an embedded dashboard preview, the description does not explain what the tool returns or the nature of 'preview'. It does not address how it differs from similar tools like 'get_embed_dashboard' or what the output format is. The description is incomplete for an agent to reliably use this tool.

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%, and the description adds no detail about the 'token' parameter beyond mentioning 'by token'. It does not explain what the token represents, how to obtain it, or any format requirements. The nested object structure is not clarified, leaving the agent without meaningful guidance.

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 specifies 'Preview an embedded dashboard by token from Metabase (admin only)', which clearly indicates the verb (preview), resource (embedded dashboard), and the method (by token). The 'admin only' constraint adds clarity. It distinguishes from siblings like 'get_embed_dashboard' and 'preview_embed_card', though could be more explicit about the difference.

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. The only hint is 'admin only', which is a prerequisite but not a usage context. There is no mention of when not to use it or which sibling to prefer for similar tasks.

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