alopeyk_get_price

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

With no annotations, the description declares it as read-only, mentions the endpoint, and lists response fields. It does not discuss rate limits or detailed auth, but adequately conveys safety for a price calculator.

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 well-structured with a lead sentence, clarification, endpoint, response, and parameter args. While slightly long, every part adds value.

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 presence of an output schema (response fields listed), the description covers return values and refers to a sibling tool for transport types. It lacks some address format detail but is largely complete.

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%, so the description compensates excellently by explaining each parameter: transport_type with examples, addresses with structure, and defaults for others.

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 'Calculate the price for a delivery between stops (read-only)' and explicitly states it does NOT create an order, distinguishing it from alopeyk_create_order.

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?

It explicitly notes that it does not create an order and requires an access_token, but does not directly compare to alternatives like alopeyk_get_batch_price. The sibling context helps infer usage.

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