run_embed_dashcard_query

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

With no annotations, the description should disclose behavioral traits like read-only vs destructive, permissions, or side effects. 'Run a query' implies execution but does not clarify if it mutates data, requires specific authentication, or has rate limits. Minimal transparency.

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 short sentence, which is concise but too brief. It front-loads the action but does not provide enough substance to justify its length. It could include a brief explanation of parameters or output.

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 no output schema and sparse parameter documentation, the description fails to provide a complete picture. It should mention the return format (query results), error scenarios, and how to obtain a valid token.

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 coverage is 0% and the description adds no meaning to the parameters. The three fields (token, card_id, dashcard_id) are unexplained. For a nested object parameter, the description should at least clarify the role of each field.

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 ('Run a query') and the resource ('embedded dashcard in Metabase'), which helps differentiate from similar tools like run_dashcard_query (non-embedded) and run_embed_card_query (single card, not dashcard). However, it does not explicitly mention the token-based authentication context.

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 (e.g., run_dashcard_query for non-embedded, run_embed_card_query for single cards). The description lacks context about prerequisites or typical use cases.

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