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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description still adds real value by disclosing that the result is recomputed at call time, that it returns what actually moved, and that Admin/PM permission is required. It does not state whether prior levelling results are reversible or how many tasks may be touched.

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?

Front-loads the consequence warning, then scope, behavior, permission, and the safety instruction in four compact clauses. No sentence is filler.

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?

No output schema, but the description tells the agent the call reports what actually moved. Permissions and the preview-first protocol are covered; the missing piece is the time horizon over which 'over-booked' is judged, which matters for a workspace-wide mutation.

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 single utcOffsetMinutes parameter is fully documented in the schema. The description adds nothing about it and never mentions that levelling is evaluated over a time window, which is the only reason the offset exists — so it neither compensates nor misleads.

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?

States a specific verb ('level the workload'), the effect ('move tasks across the whole workspace so nobody is over-booked'), and the scope (whole workspace). It is clearly distinguishable from siblings like preview_levelling or get_workload by being the applying action, though it never names preview_levelling 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?

Gives a clear pre-condition ('Preview and confirm with the user first') and the role gate ('Administrator or ProjectManager'). It stops short of naming the sibling tool to use for the preview step, leaving the agent to infer that preview_levelling is the counterpart.

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