template_preview

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

The annotations declare readOnlyHint=true and destructiveHint=false, so the safety profile is already known. The description adds nothing beyond what the annotations provide — it does not disclose what a preview entails, what it returns, or any constraints. No contradiction, but no added value either.

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 description is short, but this is under-specification rather than conciseness. It contains a single sentence that adds no information, so brevity here is not earned value — it is absence of content.

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 2-required-parameter tool with no output schema, no enum hints, and 0% schema coverage, the description fails to provide essential information about parameters, return behavior, or usage context. It is completely inadequate 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 says nothing about the 'template' or 'name' parameters — their format, meaning, or how they relate. With no schema descriptions and no parameter explanation, the agent is left entirely without semantic guidance for two required parameters.

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 'template preview' is a near-verbatim restatement of the tool name, providing no verb-resource specificity, no object of action, and no differentiation from siblings like templates_list or project_generate. It is a pure tautology.

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 whatsoever on when to use this tool versus alternatives such as templates_list or project_validate. An agent receives zero context about the conditions that select this tool over its siblings.

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