update_dashboard_layout

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

Discloses that it moves/resizes and reports per-widget outcomes, which is good given no annotations. But lacks details on side effects, authentication, or partial failure behavior.

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?

Single sentence, front-loaded with verb and resource, no fluff. Every word is functional.

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?

For a tool with two well-schemed parameters and no output schema, the description covers the core functionality and outcome. Lacks details on error handling or limits but is sufficient for basic use.

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 100%, so baseline 3. Description adds context of batch operation and per-widget outcomes but does not elaborate on parameter meanings beyond schema.

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 (move or resize multiple widgets in one call) and the resource (dashboard layout). It distinguishes from sibling tool update_widget_layout which operates on a single widget.

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?

Implies that for multiple widgets, use this tool; for single widget, use update_widget_layout. However, it does not explicitly mention when not to use or provide alternatives beyond the sibling context.

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