pricing_get

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

Beyond the readOnlyHint annotation, the description reveals that there are no rate limits and that all TLD prices are returned at once, which helps an agent understand performance and scope. This adds meaningful behavioral context without contradicting the annotation.

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 that get straight to the point. The first defines the purpose, the second emphasizes preference, and the third provides an alternative. No filler or redundancy.

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?

With no parameters, a read-only annotation, and an output schema, the description covers the essential aspects: what it does, when to use it, and how it differs from the sibling tool. It is sufficiently complete for its simplicity.

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 has zero parameters, so the description is not required to document any. The description clarifies that the result covers all TLDs and that filtering by TLD happens after retrieval, which adds context beyond the empty 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 'Get pricing for all available TLDs,' a specific verb+resource statement. It further distinguishes itself from siblings by noting it is preferred for price lookups and returns all TLD prices at once, clearly separating it from domains_check_availability.

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 explicitly states 'PREFERRED for price lookups' and 'Use this FIRST when users ask about domain costs, then filter by TLD.' It also provides a clear exclusion: 'Only use domains_check_availability when you need to verify a specific domain is actually available for purchase,' naming an alternative tool and when to use it.

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