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

The description adds valuable behavioral context beyond the annotations: it discloses a permission requirement ('when the caller can manage both endpoint teams') and an idempotent-like behavior (if an identical link exists, the existing link is returned). The annotations only supply readOnlyHint, idempotentHint, and destructiveHint flags, which do not capture this nuance. The description does not contradict the annotations.

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 the core action stated first and the duplicate-handling behavior as a concise second sentence. No wasted words or redundant repetition of schema information.

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?

Given the tool has no output schema and moderate complexity (6 parameters, creation behavior), the description covers the purpose, a key permission constraint, and a significant edge case (duplicate links). It doesn't explain error cases (e.g., what happens if the caller lacks permission) or return object shape, but for a create-type tool with minimal annotations, it is reasonably complete.

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?

The schema description coverage is 83%, so most parameters already have meaningful descriptions. The tool description reinforces that source_node_id, target_node_id, and type together define a unique link ('the same live source, target, and type'), but it doesn't add substantial new semantics beyond what the schema's per-parameter descriptions already offer. 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 starts with 'Create a process-to-process link', which is a specific verb and resource. It further clarifies the scope ('in the organization's Clarity landscape') and distinguishes from sibling tools like createClarityProcess (which creates a node) and updateClarityProcessLink (which updates rather than creates). The behavior of returning an existing link further clarifies the tool's unique role.

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 provides a clear precondition ('when the caller can manage both endpoint teams'), which is useful guidance. However, it doesn't explicitly mention alternatives like updateClarityProcessLink or when not to use this tool. The verb 'create' implies new links, but no direct comparison to sibling tools is given.

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