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

Annotations declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, and the description is consistent with that by implying a temporary resource is minted. It usefully adds that the URL is private and expires in one hour, but omits whether the link is single-use, who can redeem it, how to revoke it, and whether each call creates a new URL.

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?

One short sentence with the key qualifiers (private, one-hour) front-loaded and no filler. It is efficient, though the brevity contributes to the under-specification noted elsewhere.

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 tool that mints an access credential, the definition leaves the caller guessing about the target of the id, the scope of access the URL grants, and the returned value (no output schema exists). It covers the time limit but not enough of the tool's behavior to invoke it confidently.

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?

The single 'id' parameter has 0% schema description coverage, so the description carries the full burden and does not say what the id identifies (machine, snapshot, session?) or what format it takes. This is a material gap rather than a case where the schema already does the work.

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 and resource: create a viewer URL, qualified as 'private' and 'one-hour'. That is enough for an agent to tell it apart from siblings like ssh or screenshot, though it never names an alternative or states what the URL views.

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?

There is no when-to-use guidance, no exclusions, and no prerequisites. The agent is not told whether this is for sharing a machine console, a file, or a session, nor what it should use instead if it needs longer-lived access.

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