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

Annotations already indicate this is a write operation (readOnlyHint=false) and not fully idempotent. The description adds useful behavioral context beyond those hints: the caller permission requirement and the duplicate-handling behavior that returns the existing link. There is no contradiction with the annotations because the idempotentHint=false refers to the general operation, while the description narrows idempotency to the case of an existing live source, target, and type.

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?

The description is two sentences with no filler. The action and permission condition are front-loaded, and the second sentence provides a valuable edge-case behavior. Every sentence contributes useful information for tool selection and invocation.

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 the tool's complexity, the description covers the core purpose, the critical permission prerequisite, and the duplicate-link behavior. Required parameters and their types are already in the schema. The description could be slightly more explicit about the meaning of 'live' and what happens when the caller lacks management rights, but these are minor gaps given schema coverage and annotations.

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 high (83%), so the schema already documents most parameters. The description reinforces the importance of source, target, and type in the duplicate-check condition, but it does not add meaning beyond the schema for parameters like state, confidence, or orgId. This meets the baseline for good schema coverage without adding extra parameter-level detail.

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 states a clear action ('Create a process-to-process link') on a specific resource ('the organization's Clarity landscape'). It distinguishes this tool from siblings like createClarityProcessNode and createClarityProcessLabel by specifying that the link connects two process nodes, and it adds the uniqueness behavior for existing links.

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?

The description gives an explicit usage condition: the caller must be able to manage both endpoint teams. It also explains the behavior when the same source, target, and type already exist, which tells the agent that this tool is safe to call in that scenario. However, it does not explicitly name an alternative tool such as updateClarityProcessLink or state when not to use this tool.

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