search_dedicated_countries

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

With no annotations, the description carries the full burden. It adds meaningful context by defining dedicated numbers (private, receive SMS for ALL services, renew monthly, stay yours until cancelled) and mentions that the list includes personal monthly price and stock status. While it doesn't explicitly state that this is a read-only operation, the verb 'List' implies safety, and the added domain context goes beyond a minimal description.

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 two sentences, front-loaded with the main action, and the second sentence provides relevant background without unnecessary fluff. Every word earns its place.

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 zero-parameter list tool, the description is complete: it states what is listed (countries), the included fields (price, stock status), and gives domain context about dedicated numbers. There is no output schema, but the description gives enough for an agent to infer basic response expectations.

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?

There are zero parameters, so the baseline is 4. The description doesn't need to explain any parameters, and the schema is empty. The description adds no parameter info, but none is required.

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 uses the specific verb 'List' and clearly identifies the resource: countries where dedicated numbers are offered. It also states the included details (monthly price, stock status), making it distinct from sibling tools like search_sms_services or purchase_dedicated_number.

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 for when to use the tool—when needing to see countries with dedicated numbers—and explains what a dedicated number is, which helps with scope. It does not explicitly mention alternatives or when not to use it, but the purpose is clear enough for an agent to make a basic choice.

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