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

Annotations only mark this as non-read-only, non-destructive, and not open-world; the description adds substantial behavioral context beyond that: single-use, two-week expiry, passkey requirement at redemption, and the ownership transfer effect. These constraints materially change how an agent should handle the tool and are not derivable from the annotations or schema, and nothing here contradicts 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?

Four short sentences, front-loaded with what the link is and its effect, followed by handling rules and the alternative path. Every sentence carries information, though the opening could have led with the tool's action verb for faster orientation.

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?

With no output schema, the description adequately covers the return artifact ('a link'), its validity (single-use, two weeks), and the redemption requirement (passkey). The auth nuance is covered by the parameter schema. It could more explicitly state that the response contains the link, but nothing essential to calling it correctly is 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?

There is one parameter and schema description coverage is 100%, so the schema already explains the site token and the Authorization-header fallback. The description adds no parameter-level detail, so the baseline of 3 applies.

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 is written as a noun phrase describing the artifact ('A link that makes whoever opens it the owner...') rather than stating the tool's action. An agent can infer the tool yields an invite link it should hand to the future owner, but no explicit verb like 'create' or 'returns' is ever used, so the purpose is implied rather than stated. The resource domain and its effect are clear, which keeps it above a vague rating.

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 gives concrete usage direction: 'Give it to the person who should own the site, never post it,' which states both the intended recipient and a prohibition. It also supplies a clear when-not path: 'Once the site has an owner, they invite others from its settings,' routing the agent away from this tool in that case. It does not name a sibling tool, so it falls short of a 5.

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