Get template details

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds little beyond restating the purpose ('detailed information' and 'specific template specifications') and does not disclose response contents, error behavior, or any other operational details. With no output schema, this omission weakens transparency.

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 two concise sentences, front-loaded with the purpose and usage context. Every phrase earns its place, with no redundancy or fluff.

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 simple read-only tool with one required integer parameter and annotations covering safety, the description is adequate. However, it lacks details about what 'detailed information' includes (fields, structure) or any prerequisites, which is noticeable since no output schema exists. It is functional but not rich.

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 100% as templateId has a description. The tool description adds no additional meaning about the parameter, such as where to obtain it or its format, relying entirely on the schema. This is acceptable given full coverage, but no extra value is contributed.

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 clearly states it retrieves detailed information about a specific OS template for virtual machines, using the verb 'Retrieve' and specifying the resource. It distinguishes from the likely sibling VPS_getTemplatesV1 by emphasizing 'specific' versus a list, though it does not explicitly name the alternative.

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?

The description provides a usage context: 'Use this endpoint to view specific template specifications before deployment.' This indicates when to use it, but it does not mention alternatives (e.g., VPS_getTemplatesV1 for listing) or scenarios where this tool should not be used, leaving some ambiguity.

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