search_embed_dashboard_param_values

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

No annotations provided, so description carries full burden. It says 'Search values' implying read-only query, but doesn't disclose rate limits, error handling, or output format. Minimal behavioral info.

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?

A single sentence, no fluff. However, the brevity is harmful given the lack of parameter descriptions and missing usage guidance. It sacrifices clarity for conciseness.

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?

With no output schema, no annotations, and 0% schema coverage, the description is insufficient. An AI agent lacks critical information about how to invoke it correctly, especially given many similar sibling tools.

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 description adds no parameter details. The three fields (token, param_key, query) are unexplained. An AI agent must guess their meaning, leading to high risk of misuse.

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 states it searches values for a parameter of an embedded dashboard, which is specific. It distinguishes from siblings like search_dashboard_param_values or search_card_param_values by specifying 'embedded dashboard', but 'search' could be clearer (e.g., filtering vs autocomplete).

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 vs alternatives like search_embed_card_param_values or get_embed_dashboard_param_values. No prerequisites or context like needing an embedding token.

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