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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety bar is low. The description still adds meaningful behavior: the tool performs no action itself, it emits human-readable navigation steps (screens, buttons, fields), and the actual mutation must be carried out through cotlet_browser_* tools. That is consistent with, and richer than, 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 critical constraint ('opens nothing by itself') is front-loaded right after the purpose, and the follow-up tool family is named in the same sentence. The trailing note on tl;dv's public REST API and hosted MCP server being read-focused is somewhat tangential but does justify why the browser route is required.

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 zero-parameter tool with full annotation coverage and no output schema, the description covers what the tool returns, what it does not do, and which sibling tool family completes the task. The main omission is the meeting-scoping question — nothing tells the agent what context must be established before calling it.

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?

With zero parameters and 100% schema coverage, the baseline applies; the description adds the useful clarification that the output is procedural guidance rather than a performed share. The only gap is that it never explains how the specific meeting to share is determined when no input is supplied, leaving the agent to infer it comes from session context.

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 states a specific verb+resource ('Share meeting in the user's own tl;dv account') and immediately clarifies the non-obvious nature of the operation: it returns step-by-step instructions rather than performing the share. It is distinguishable from siblings like tldv_create_clip or tldv_get_transcript, though it never says how the target meeting is identified (no parameters exist), which leaves a residual ambiguity.

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?

Explicitly tells the agent how this tool fits into a workflow: 'opens nothing by itself; then do it with the cotlet_browser_* tools in the user's tl;dv Cloud Browser.' That is a concrete when-to-use and what-to-do-next. It stops short of naming when NOT to use it (e.g., when the official API/MCP path suffices, other than the parenthetical note that those are read-focused).

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