list_prepurchase_os_templates

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

Describes what it returns (slug, display name, version) and scope (prepurchase, legacy products). No annotations provided, but description covers typical read behavior. Minor omission: not explicitly stating it's read-only, but implied.

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?

Three sentences, each with a clear purpose: what it does, when to use, and alternative/source. No unnecessary words, front-loaded.

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?

Complete for a simple 1-param tool with no output schema. Covers purpose, usage, alternatives, and what fields are returned. Meets all needs.

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 already describes parameter fully. Description adds context: 'sku comes from list_catalog_products', linking to another tool. Adds value beyond schema.

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?

Clearly states it lists OS templates selectable at purchase time for legacy VPS/dedicated-server SKU, with specific fields (slug, display name, version). Distinguishes from sibling list_os_templates by specifying context.

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 says when to use (before ordering) and when not (for already-running server, use list_os_templates with service_id). Also tells where to get the sku (list_catalog_products).

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