search_embed_card_param_values

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

No annotations are provided, so the description must disclose behavioral traits itself. It does not state whether the operation is read-only, whether it requires authentication, any rate limits, or what the response looks like. The single sentence lacks necessary behavioral context.

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 that is concise and front-loads the verb 'Search'. However, it is too brief and could benefit from more structure, such as listing the parameters or usage context.

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 tool's complexity (nested parameter, no output schema, high number of siblings), the description is incomplete. It does not explain the purpose of the nested object, the role of each parameter, or what the search returns. The description fails to compensate for the lack of schema coverage and output schema.

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 input schema has a nested object with three required fields (query, token, param_key), but the description does not explain the semantics or expected data types of these fields. Schema coverage is 0%, so the description adds no value in clarifying parameters.

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 (search) and the resource (values for a parameter of an embedded card in Metabase). It effectively distinguishes this tool from siblings like search_card_param_values and search_dashboard_param_values by specifying 'embedded card'.

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 alternatives such as search_card_param_values or search_embed_dashboard_param_values. There is no context about prerequisites, when not to use, or scenarios where this tool is appropriate.

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