get_embed_dashboard

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

No annotations are provided, and the description does not disclose any behavioral traits such as side effects, security requirements (beyond the JWT token), or whether the operation is read-only. The description is too minimal to offer transparency about the tool's 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 concise with a single sentence, but it is overly brief. Important information (e.g., what the response contains) is omitted. It could be expanded without losing conciseness to include key details.

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 and annotations, the description is insufficient. It does not explain what the tool returns (e.g., a JSON dashboard object or HTML), which is essential for an agent to understand the outcome. The complexity of the Metabase API warrants a more complete description.

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 schema has 0% description coverage for the parameter 'token'. The description adds that the token is a JWT token from Metabase, which is basic. No additional details about format, validity, or constraints are provided, so it only marginally adds value over the schema.

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 'Get' and the resource 'embedded dashboard', specifying the use of a JWT token. It distinguishes itself from sibling tools like 'get_embed_card' by focusing on dashboards. However, it does not specify what exactly is returned (e.g., dashboard data, HTML), leaving some ambiguity.

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?

The description provides no guidance on when to use this tool versus other related tools such as 'get_embed_dashboard_query', 'get_embed_dashboard_tile', or 'get_embed_dashboard_params'. An agent lacks context to differentiate among them, which is critical given the many sibling tools.

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