Get Pricing

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered without the description's help. The description adds useful content context (hourly rates plus volume tiers), which suggests a static catalog rather than account-specific data, but it does not say whether results vary by region, account, or currency.

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?

A single short sentence that front-loads the verb and resource and then names the two data categories returned. No filler or redundant restatement of the title.

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 no-parameter read tool with full annotation coverage, the description is adequate but thin. With no output schema, it leaves unclear whether pricing is region-specific (siblings include list_regions) or account-scoped, and says nothing about currency or units.

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 tool takes no input parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. It correctly implies the pricing scope is determined by the service itself rather than by caller-supplied filters.

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?

Uses a specific verb ('Get') and resource ('pricing') and further specifies the content returned: per-resource hourly rates and volume pricing tiers. This clearly distinguishes it from every sibling, none of which deal with billing or rates.

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?

Provides no explicit when-to-use statement or alternatives, but for a zero-parameter global lookup the usage is largely self-evident from the purpose sentence. No exclusions or prerequisites are stated, so it remains implied rather than guided.

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