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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds the crucial specific: creating a new link invalidates any prior active link for the process, i.e. exactly what gets destroyed. It also discloses the authorization requirement. It stops short of 5 because it says nothing about the return value or the shape of the created link, which matters since no output schema exists.

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 followed immediately by the permission constraint and the destructive side effect. Every clause earns its place.

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 single-parameter mutation whose annotations already flag it as destructive, the description covers action, authorization, and the invalidation side effect well. The one gap is the missing description of what is returned (a link, its scope, expiration), which is more noticeable given there is no output 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?

There is a single required parameter (process_id) with 100% schema description coverage, so the schema already carries the semantics. The description's phrase "process-scoped" corroborates the parameter but adds no format, constraint, or sourcing detail beyond the schema — the expected baseline of 3.

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 names a specific verb and resource ("Create or regenerate a process-scoped Clarity interview invite link") and adds the regeneration capability, which cleanly separates it from sibling tools like createClarityProcessLink and createTeamInviteLink. It does not explicitly name those alternatives, so it stops short of full sibling differentiation.

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 states a real precondition — only the process creator or team managers can create invite links — which tells the agent when this call will succeed. What's missing is routing guidance: it never says when to prefer this over sendClarityInterviewInvites, getClarityProcessInviteLink, or the delete counterpart.

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