hcloud_get_pricing

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

The annotations already declare this is a safe, read-only, open-world read. The description adds genuinely useful context beyond that: prices are calculated using the Project owner's VAT and currency, and both net and gross figures are returned. It does not discuss pagination behavior, but the schema parameter covers that.

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 short sentences, front-loaded with the core action, then the scope, then the output caveats. No redundant or filler 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 one-parameter read-only tool with no output schema, the description covers what is returned (prices for all resources, net and gross) and the currency/VAT basis. It stops short of describing the response structure or pagination effects, which would help since no output schema exists.

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?

The single parameter (auto_paginate) has 100% schema description coverage, so the baseline of 3 applies. The description does not mention auto-pagination or how pages are merged, adding no meaning beyond the 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?

The description opens with a specific verb and resource ('Get all prices') and scopes it to 'all resources available on the platform'. No sibling tool covers pricing, and the resource is unambiguous, so an agent can select it immediately.

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 scope ('all resources available on the platform') makes it clear this is a global pricing lookup with no filtering, and no sibling offers an alternative pricing path. There are no exclusions to state, but the description never explicitly says when to reach for it versus other getters.

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