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

Annotations only supply the generic safety profile (readOnly=false, destructive=false, idempotent=false), and the description adds real behavioral detail: name validation occurs before any write, and the four operation kinds are applied in a fixed order (rename, remove, update, add). It stops short of stating permission requirements or whether a removed widget can be recovered, which matters for the remove path.

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?

Three sentences, no filler, front-loaded with the primary purpose and then the operational semantics. The ordering rule is stated once and compactly rather than expanded into prose.

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 nested widget arrays, no output schema, and mutation semantics, the description covers the essentials an agent needs: partial updates, id source, layout semantics, validation-before-write, and write ordering. It leaves gaps around failure behavior (duplicate names, name collisions on rename) and what an empty result looks like.

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 only 33%, so the description has to carry weight, and it does explain the key semantic: update entries key off a widget id and are partial, and position moves or resizes. It says nothing about baseId, dashboard, or the distinction between remove and add entry shapes, leaving three of six top-level parameters supported only by the 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 states a specific verb and resource ('Rename a dashboard') and enumerates the full operation set: add, change, move, remove widgets. That distinguishes it cleanly from create_dashboard, get_dashboard and list_dashboards without needing to name them.

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?

It gives concrete usage context: widget ids come from get_dashboard, and 'only the settings you pass change' tells the agent this is a patch-style update rather than a full replace. It never names an alternative tool or an explicit when-not-to-use case, which keeps it short of a 5.

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