get_preview_embed_card_param_remapping

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

No annotations provided, so the description carries full burden. It implies a read operation ('get') but does not disclose any behavioral traits such as authentication needs, rate limits, or return format. Minimal disclosure.

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 short (one sentence) and front-loaded, but it lacks substance. It is concise but not sufficiently informative for a tool with nested parameters and no annotations.

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 has nested objects, no output schema, and no annotations, the description is incomplete. It does not explain what a 'remapping' is, what the response contains, or any dependencies.

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% per context (though the schema itself has brief descriptions for token and param_key). The description adds no parameter explanation beyond what the schema provides, leaving the agent to rely solely on parameter names.

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 'Get remapping for a parameter of a preview embedded card', clearly indicating the verb ('Get') and resource (remapping for a preview embedded card parameter). However, it does not distinguish from the sibling tool 'get_embed_card_param_remapping', which is identical except for 'embed' vs 'preview embed'.

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 (e.g., get_embed_card_param_remapping for actual embeds). No prerequisites or context provided.

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