get_vps_pricing

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds the context that this is a preview tool for resize_vps, but doesn't disclose details like whether pricing is estimated or exact, or whether it reflects current vs. projected costs. No contradiction with annotations.

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 a single sentence that front-loads the core purpose and immediately adds usage context. Every word earns its place; no fluff or repetition.

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 parameter and no output schema, the description is mostly adequate. However, it doesn't clarify what 'pricing' includes (e.g., hourly/monthly, with or without disks) or whether the returned price is for the current configuration only. Given the sibling get_vps_billing exists, a bit more distinction would help.

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%, so the description carries the burden for parameter semantics. However, the single parameter vps_id is self-explanatory given the tool name and description. The description doesn't add detail about the format or constraints of vps_id, but with only one obvious parameter, the gap is minor.

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 the tool returns current pricing for a VPS configuration, using a specific verb ('get') and resource ('pricing'). It distinguishes itself from the sibling resize_vps by explicitly mentioning it's useful before resizing, though it doesn't explicitly name the sibling.

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 clear context: it's useful before calling resize_vps to preview cost. This implies when to use it, but it doesn't explicitly state when not to use it or mention alternatives like get_vps_billing or get_vps_backup_cost.

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