alopeyk_get_batch_price

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

With no annotations, description must disclose behavior. It correctly states read-only and no order creation, but does not cover potential rate limits, error handling, or side effects beyond that.

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?

Description is concise with key info front-loaded. Two short paragraphs plus bullet. Could be more structured but no excess words.

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 batch pricing tool with an output schema, it covers the limit, order shape, read-only nature, and auth requirement. Lacks mention of error scenarios 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%, but description adds meaning: orders must be max 15 objects shaped like alopeyk_get_price body (transport_type + addresses + flags). Instance parameter is explained as 'Configured instance to use (default when omitted).'

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 it calculates prices for up to 15 orders in one call and is read-only. It distinguishes itself from alopeyk_get_price (single order) and alopeyk_create_order (creates orders) by saying 'This does NOT create orders.'

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 mentions read-only, requires access_token, and max 15 orders. It implicitly compares to alopeyk_get_price for batch vs single, but does not explicitly state when not to use or list alternatives beyond that.

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