search_embed_dashboard_params

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It states the tool 'searches' but does not mention read-only nature, authentication requirements (JWT implied but not explicit), or side effects. The return format and pagination behavior are omitted.

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 concise sentence with no wasted words. However, it could be slightly expanded to include key usage notes without sacrificing brevity.

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 nested input schema, lack of output schema, and zero annotations, the description is insufficient. It fails to explain how this tool differs from similar search tools (e.g., search_embed_card_param_values) or what the response contains, leaving the agent underinformed.

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% for the top-level 'input' property, though nested properties have descriptions. The description adds no extra meaning beyond the schema's own property descriptions (token, param_key, search_string). It does not explain constraints like token expiry or search string format.

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 verb 'Search' and resource 'parameter values for a parameter in an embedded dashboard from Metabase'. It precisely distinguishes this tool from siblings like search_card_param_values (card context) or search_dashboard_param_values (non-embedded dashboard).

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 the many similar search siblings (e.g., search_embed_card_param_values, search_preview_embed_dashboard_param_values). The agent receives no help in deciding which search tool to invoke.

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