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

Annotations declare it is a non-read-only, non-destructive, non-open-world operation; the description adds genuinely new behavior by stating it returns the link, reuses an existing link rather than creating a duplicate, and discloses cost (free unless a brief is generated at ~0.5 credit). That cost and side-effect disclosure (writing a brief) is exactly the kind of context annotations cannot carry.

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 purpose and the no-account constraint are front-loaded in the first sentence, followed by audience examples, the brief option, return value, reuse behavior, and cost in a tight sequence. It is dense but every sentence carries a distinct fact; slightly packed but no filler.

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 five parameters, one enum, and no output schema, the definition covers return value ('Returns the link'), the free-vs-paid distinction, and link reuse, so an agent has enough to call it correctly. Remaining gaps (expiry behavior, document-id format) are minor and partly covered by the 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?

Schema coverage is 100%, so the baseline is 3, but the description adds relational meaning beyond the schema: it explains that with_brief pairs with audience 'client' and that the resulting brief is shared alongside the plan, and that 'latest' is the default document for a client. That stitching of parameter interactions is real added value.

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 and resource ('Create a shareable link to a session') with the key scope qualifier that recipients need no Metodic account. This clearly separates it from sibling generators like session_one_pager or generate_handout, which produce artifacts rather than external access 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?

Names concrete use cases (client/sponsor approval, co-facilitator, participants) and notes the 'client' audience is the default and most common, which is useful routing context. It stops short of naming an alternative sibling tool or stating when not to use it, so it is clear context without explicit exclusions.

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