search_available_numbers

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

With no annotations and a sparse description, behavioral traits (e.g., read-only nature, pagination, rate limits) are not disclosed. The description does not indicate whether the operation mutates data or requires specific authorization.

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 concise (one sentence) but overly minimal. It lacks structure or detail, though it avoids verbosity. Could be expanded to include key usage notes without losing conciseness.

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 4 parameters (one required), no enums, and an output schema, the description is insufficient. It does not explain how search results are filtered, what the output contains, or how to interpret results.

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?

Schema coverage is 0% (no property descriptions), and the description adds no parameter-level meaning. Parameters like locality and phone_number_type are self-explanatory but the description fails to clarify expected values or constraints.

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 clearly states the verb 'Search' and resource 'available phone numbers' with the intent 'to purchase', distinguishing it from sibling tools like list_phone_numbers (owned numbers) and order_phone_number (purchase). However, it could be more specific about search criteria.

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?

No guidance on when to use this tool versus alternatives. It does not mention prerequisites or exclusions, leaving the agent to infer context from sibling names alone.

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