smm_quote

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

No annotations are provided, so the description carries the full behavioral burden. The only signal is the '(free)' tag, which hints there is no cost or side effect, but it never states that this is read-only, places no order, or guarantees pricing accuracy. With zero annotation coverage, this is a substantial gap.

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 sentence is short and front-loaded, but the duplicated '(free) (free)' is pure noise and suggests generated tag artifacts rather than deliberate content. Minimal but not wasteful beyond that duplication.

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 two-param lookup with no output schema, the description still omits what the response contains (price, currency, minimum/maximum quantity) and how to obtain a valid serviceId. An agent cannot invoke this confidently without discovering serviceId elsewhere.

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 0%, so the description must compensate, and it only restates the two parameter names from the schema. It does not explain where serviceId comes from (presumably smm_services), whether quantity is units/1000s, or any valid ranges.

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: 'Get the price' for a given serviceId and quantity. An agent can tell this is a pricing lookup rather than an order, refill, or status call. It does not, however, name any sibling or clarify how it differs from the many adjacent quote/pricing tools (sms_quote, sms_pricing, sms_rental_quote).

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?

There is no guidance on when to use this versus smm_service_details (to discover the service), smm_order (to actually purchase), or the parallel SMS quote tools. No prerequisites, no ordering context, no exclusions. The agent must infer its role from the name alone.

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