get_embed_dashboard_param_remapping

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

No annotations are present, and the description does not disclose any behavioral traits beyond the action. It does not mention authentication requirements, idempotency, side effects, or output format, which is necessary for a tool with no schema descriptions.

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 concise with a single sentence, but it lacks structure. It could be more useful with additional context about input/output, but it is not overly verbose.

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 lack of annotations and output schema, and the complexity of param remapping with many sibling tools, the description is incomplete. It does not explain what remapping does, prerequisites, or result format.

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 requires 'token' and 'param_key', but neither parameter is described in the schema (0% coverage) nor in the description. The description adds no meaning to these parameters, leaving the agent to guess their significance.

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 'Get' and the resource 'remapping for a parameter of an embedded dashboard', which is specific. However, it does not differentiate from sibling tools like 'get_dashboard_param_remapping' or 'get_embed_card_param_remapping', which have similar purposes.

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 alternatives. With many sibling param remapping tools, the description should mention what distinguishes this from others, such as the fact that it operates on embedded dashboards specifically.

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