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

The annotations already flag this as non-read-only, non-idempotent, and destructive. The description adds genuinely new context beyond annotations: renaming a landscape-linked folder "permanently stops landscape name-sync," an irreversible side effect an agent could not infer from structured fields. It does not describe permissions or the response, keeping it from a 5.

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 short sentences, zero waste. The core action is front-loaded and the destructive side-effect caveat immediately follows, so nothing needs to be re-read.

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 simple rename with full schema coverage, no output schema, and annotations carrying the safety profile, the description covers what the tool does and the one non-obvious irreversible consequence. It omits any auth/team-scoping guidance, but that lives in the schema.

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 folderId, name, and the non-obvious team_id fallback/rejection behavior are all documented in the schema. The description adds no syntax or constraint detail beyond what the schema provides, so the baseline 3 applies.

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+resource ("Rename a process folder") that distinguishes it from createClarityFolder, deleteClarityFolder, and reorderClarityFolders. It also clarifies beyond the generic title "Update Clarity Folder" that the only operation is a rename. Sibling alternatives are not named, so it falls short of a 5.

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?

Usage is implied: call this to rename a folder. There is no explicit when-to-use, when-not-to-use, or pointer to sibling tools (e.g. moveClarityProcessesToFolder for relocation), and no stated prerequisites such as required permissions.

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