create_preview_session

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

No annotations are provided, so the description carries full burden here. It discloses that the tool creates a token (implying a side effect — a new session is created), but gives no detail on authorization requirements, whether the token expires, HTTP failure modes, or the response shape. Barely above nothing for a state-changing operation.

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 endpoint included — no wasted words. The HTTP method and path are useful operational context. It's appropriately short, though it leans toward under-specification rather than efficient completeness.

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 generating a token, the agent needs to know what the response contains and how parameters constrain it. With no output schema, no annotations, and 0% parameter coverage, the description leaves those gaps open. Incomplete for correct invocation.

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 description coverage is 0% and the description adds zero meaning to the two parameters (versionId, templateId). An agent cannot tell which is required, how they relate, or what values are valid. The description does not compensate for the missing schema documentation.

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 clear verb-resource pair: POST /template-preview/session generates an external share preview token. The purpose is comprehensible and distinct from siblings — no other tool name mentions 'preview_session'. However, it doesn't articulate how it differs from the many template-related siblings in terms of scope.

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?

No guidance is given on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing a logged-in session, existing template/version) or when creating a preview token is appropriate. An agent gets no directional help.

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