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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is largely covered. The description adds that the change is persisted immediately and must be justified in 'reason', plus the skill prerequisite, but leaves out what happens if every optional field is omitted, whether permissions or approval are required beyond the approval card hinted at in the schema, and how partial updates treat unmentioned fields.

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?

Two sentences, tightly front-loaded: the operation set comes first, and the persistence plus skill prerequisite follow. No redundant restatement of the name or schema.

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 9-parameter mutation tool with no output schema, the definition covers the operation set, persistence, and the required workflow prerequisite, and annotations cover the safety profile. The main remaining gap is that all eight mutable attributes are optional yet the description never states whether a call with none of them is valid or a no-op.

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 67%, with the key parameters (icon, color, index, parentId, folderId, reason, projectId, environment) already documented in the schema; only 'name' lacks an inline description, and its constraints are self-evident. The description's enumeration of updatable attributes mirrors the schema rather than adding new semantics such as whether at least one field must be supplied.

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 names the resource (a dashboard folder) and enumerates the specific operations: rename, change icon or color, move under another folder, reorder among siblings. This is clearly distinct from siblings such as create_dashboard_folder, delete_dashboard_folder, update_dashboard, and move_dashboard, which targets dashboards rather than folders.

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 an explicit prerequisite: load the manage-dashboards skill via load_skill("manage-dashboards") before calling. It also states the effect is saved (persisted) when run, which signals this is a real mutation rather than a preview. It stops short of naming when-not-to-use cases or pointing to siblings such as update_dashboard for non-folder changes.

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