purchase_dedicated_number

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

With no annotations, the description carries the full transparency burden. It discloses the quote-then-commit behavior with max_price_cents protection, the return format (ded_xxx id), and the follow-up polling action. This is valuable beyond the schema, though it omits edge cases like failure modes or refund policies.

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 three concise sentences, front-loaded with the core purpose, followed by the unique behavioral selling point and return/next-step guidance. Every sentence earns its place with zero filler.

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?

Given the lack of annotations and output schema, this description does a good job explaining the purchase flow, output ID, and how to consume it. It doesn't cover every aspect (e.g., auto-renew behavior) but the schema handles auto_renew. The overall context is sufficiently complete for an agent to invoke the tool correctly.

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 schema already documents both parameters (country and auto_renew) with descriptions, at 100% coverage. The description merely echoes 'in a country from search_dedicated_countries' which adds no new semantic meaning beyond the schema's parameter description. Baseline 3 is appropriate.

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 'Buy a dedicated monthly number in a country' which is a specific verb+resource+scope. It also references search_dedicated_countries as the source and mentions returns 'ded_xxx id', clearly distinguishing it from sibling tools like get_dedicated_number (which reads SMS) and rent_number (rental).

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 clearly states that this tool is for buying dedicated numbers sourced from search_dedicated_countries, implying when to use it. However, it does not explicitly mention when not to use alternatives or list exclusions, so it falls short of full guidance with explicit alternatives.

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