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

Annotations only declare it is a non-read-only, open-world, non-destructive operation; the description goes well beyond that by disclosing the two payment paths, the exact key-activation sources (buy_credits, use_api_key, Bearer header), the x402 USDC-on-Base PAYMENT_REQUIRED handshake, and the returned phone/id/pollToken. This is the auth and billing context an agent needs before invoking.

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?

Front-loaded with the core action and efficient overall, but the parenthetical list of key sources makes one sentence long and dense. No wasted sentences, though the payment-branch explanation is compressed into a single run-on.

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?

There is no output schema, so the description carries the return contract and does so (phone, id, pollToken), names the next tool to call, and names the alternative for a different caller class. For a 6-param, 3-required mutation with a two-step payment flow, nothing essential is missing.

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 description coverage is 100%, so the baseline is 3; the description adds real meaning on top by explaining how apiKey becomes active and what paymentHeader is for in the retry flow. It does not, however, clarify country resolution defaults or the purpose enum beyond what the schema already lists.

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?

States a specific verb and resource ("Rent one virtual number for a lawful SMS verification") and immediately distinguishes itself from the sibling it is not for ("Signed-in human accounts should use ucode_sms_rent_with_credits instead"). An agent can separate this from ucode_sms_rent_packages, ucode_sms_rent_with_credits, and ucode_sms_rent_provider_direct without opening any schema.

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?

Gives explicit when-to-use branches: with an active uc_live_ key it pays from the agent wallet; without a key it falls into pay-per-SMS and must be retried with paymentHeader. It also names the alternative tool and the condition that selects it, plus the follow-up call to ucode_agent_check_sms.

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