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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive mutation, and the description adds real context beyond that: the folder is created immediately when the call runs, and the reason string appears on a user-facing approval card, implying a human-in-the-loop gate. The 6-level nesting constraint adds another behavioral limit. It stops short of describing the return value or collision behavior on duplicate names.

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 short sentences, front-loaded with the core action and constraint, then the mutation/approval note, then the prerequisite. Very little waste; the middle sentence is slightly compressed but still readable.

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 an 8-parameter mutation with no output schema but full schema coverage, the description supplies purpose, the nesting depth cap, the approval-card semantics of reason, and the required skill prerequisite. What is missing is minor: whether the new folder id is returned and how name conflicts are handled.

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 100%, so the schema already explains name, color, icon, index, parentId, projectId, and environment in detail. The description only restates that nesting is capped at 6 levels (already in the parentId description) and that reason should be one explanatory sentence (already in the reason description). Baseline 3 is appropriate.

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 opens with a specific verb+resource: 'Create a dashboard folder,' plus the key qualifier that it may be nested (max 6 levels). This is clearly distinct from create_dashboard and update_dashboard_folder by resource and operation, though it never names those siblings explicitly.

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 a genuine workflow prerequisite ('Load the manage-dashboards skill first'), which tells the agent when in the process to call this. However, there is no guidance on when to use create_dashboard_folder versus create_dashboard or update_dashboard_folder, nor any exclusion or alternative routing.

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