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

Annotations only declare readOnlyHint=false, destructiveHint=false, openWorldHint=false; the description adds behavioral facts those don't carry, namely that creation implies consent to be invited and that rotation replaces (invalidates) the prior link. It says nothing about auth expectations or whether the returned link expires, but the added context is meaningful for a mutating call.

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?

A single front-loaded sentence with the core action first and the two flag behaviors attached via semicolons. No filler, no restatement of the name or title.

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?

No output schema exists, so the description would ideally say what comes back, though 'invite link' makes the return value reasonably evident. With zero required parameters and a low-coverage schema, the description plugs the main gaps; only expiration/auth details are missing.

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 33%: only 'token' is documented in the schema, and the description compensates by defining both previously undescribed parameters ('create' makes one, 'rotate' replaces it). The 'token' parameter's guidance is already handled well in the schema, so only minor syntax gaps remain.

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 ('Get') and resource ('your builder invite link'), and the conditional flags make the scope concrete. It names no sibling, so an agent can't tell from this text alone how it relates to the rest of the toolset, but the purpose itself is unambiguous.

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 explains the semantics of the flag combinations ('create:true makes one', 'rotate:true replaces it'), which effectively signals the three usage modes. However, it never states prerequisites, when not to use it, or which sibling to prefer for adjacent tasks, so usage is implied rather than spelled out.

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