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

Annotations only declare the write flags; the description adds the real behavioral constraint — the authorization tiers required for an active area versus a proposal. It does not mention side effects of creating an active area (duplicate detection, whether an existing area is returned), which the schema partially covers.

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, no filler, with the core action front-loaded and the mode/permission caveat immediately after. Every clause carries information an agent needs.

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 mutation tool with no output schema and six parameters, the description covers permissions and mode selection but leaves the hierarchy semantics (parentId null behavior) and the result of the call unaddressed. Adequate but with visible gaps.

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 coverage is only 33%, so the description must carry more weight than it does. It explains creationMode well (default, what proposal means, permission implications) but adds nothing about parentId (is null the root?), ownerLabel, orgId, or name constraints.

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 and resource: 'Create an area folder in the process tree.' An agent can tell what object is produced, though the description does not explicitly distinguish this from near-siblings like createClarityFolder or createClarityProcessNode.

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 concrete decision rule for the active vs proposal modes tied to permissions, which is exactly the branch an agent must choose. It stops short of naming alternative tools (e.g. proposeClarityLandscapeProcess) for when a proposal is the better route.

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