get_embed_card_param_remapping

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

No annotations provided, and the description gives no behavioral traits beyond the read operation. It does not disclose auth requirements, error conditions (e.g., invalid token), or performance implications.

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 extraneous information. However, it could be slightly improved by including more context while remaining concise.

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 complexity of embedded card parameter remapping, the many sibling tools, and lack of output schema, the description is incomplete. It omits return value structure, usage examples, and how it differs from similar 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?

The description adds no meaning beyond the schema; it merely restates 'parameter of an embedded card'. With 0% schema description coverage for the top-level parameter, the description should compensate but fails. Inner parameter descriptions exist in schema, but the outer 'input' is undocumented.

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 remapping' and the resource 'parameter of an embedded card in Metabase'. It distinguishes from siblings like get_card_param_remapping (non-embedded) and get_embed_dashboard_param_remapping (dashboard vs 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?

No guidance on when to use this tool versus the many sibling tools (e.g., get_card_param_remapping, get_embed_dashboard_param_remapping). No mention of prerequisites such as needing an embed token or that this is for embedded cards specifically.

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