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. It only states that the tool calculates cost and time; it does not disclose return format, assumptions, caveats, or whether the operation is read-only. The non-destructive nature is implied by 'Расчёт' but not elaborated.

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?

A single clear sentence with no filler, redundant schema repetition, or boilerplate. It is front-loaded with the core purpose.

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?

Despite complete parameter documentation, the absence of an output schema, annotations, and usage or limitation guidance leaves the description at a bare-minimum level. An agent lacks context about what the response contains, any calculation assumptions, and when this tool is preferable to siblings.

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?

The description adds no parameter-level details, but the input schema covers 100% of parameters with names, units, defaults, and descriptions. Therefore the baseline of 3 applies: the schema does the heavy lifting.

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 names a specific action ('Расчёт' – calculation) and a specific resource ('стоимости и сроков доставки Boxberry' – Boxberry delivery cost and time), which clearly separates it from siblings like list_cities, list_points, and track.

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?

The description implies the tool is for calculating Boxberry delivery costs and times, but it does not explicitly state when to choose it over sibling tools or mention any prerequisites, exclusions, or alternative routing.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It accurately states the core behavior: listing cities and searching by name. However, it does not mention output format, pagination, or whether an empty search returns all cities, leaving some behavior implicit.

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 a single concise sentence with no filler, and the core resource is front-loaded. It is appropriately sized for a simple tool, though it could add a useful detail about the return value without becoming verbose.

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 low-complexity tool with one optional parameter, the description is mostly adequate. However, with no output schema and no annotations, it does not specify what fields the returned city list includes or how search behaves at boundaries, leaving a moderate gap for an agent interpreting 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?

The input schema documents the one parameter with 100% coverage, so the description adds little beyond restating the search-by-name functionality. It reinforces the substring search concept but does not provide extra detail, examples, or constraints beyond what the schema already offers.

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 identifies a list operation over Boxberry cities with optional search by name. The resource 'cities' distinguishes it from sibling tools like list_points and list_services, though it does not explicitly name those alternatives. Using a noun phrase instead of a verb is slightly weaker, but the intent is unambiguous.

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?

The description implies the tool is for retrieving Boxberry cities with optional name filtering, but it gives no explicit guidance about when to choose this tool over alternatives such as list_points or zip_check. An agent can infer the usage from the tool name and resource, but exclusions and selection criteria are not stated.

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

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

With no annotations, the description carries the full behavioral disclosure burden, but it only says the tool returns a list of pickup points in a city. It does not mention the prepaid filtering behavior (left to the schema), response contents, pagination/limits, or failure behavior, so it is minimally transparent rather than misleading.

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 a single sentence with no filler; the object (pickup points) and scope (city) are front-loaded. This is appropriately sized for a simple list operation.

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?

The definition is adequate for a simple list call when combined with the schema, but because there is no output schema and no annotations, the description should more clearly state the full return behavior and the dependency on list_cities. It leaves room for ambiguity about whether all points or only some are returned.

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%: city_code is described as the Boxberry city code from list_cities, and prepaid has enum/default plus a clear Russian explanation. The description adds no parameter-level meaning, so it appropriately rests at the baseline 3 for full schema coverage.

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 names a specific resource (Boxberry pickup points) and a clear scope (specified city), with an implicit list verb. This is immediately distinguishable from siblings like list_cities (cities) and calc_delivery/track (delivery calculations/tracking).

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 explicit when-to-use or when-not-to-use guidance is given, and no alternative tool is named in the description. The schema's note that city_code comes from list_cities provides a workflow hint, and the city-based scope implies usage for listing pickup points, but the selection guidance is mostly left to inference.

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

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

With no annotations, the description carries the full behavioral disclosure burden. It only states that a list of rendered services is returned, without mentioning that the operation is read-only, whether authentication is needed, error behavior, or response format.

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 a single short sentence with no wasted words. It is appropriately concise and front-loaded for a simple one-parameter tool.

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 tool with no output schema and no annotations, the description is too thin. It does not explain what 'services' means in the Boxberry context, what the output will contain, or any likely failure scenarios, leaving the agent without enough context to invoke it confidently.

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?

The schema covers the only parameter with 100% description coverage. The tool description adds no extra meaning beyond what the parameter description already provides, so the baseline of 3 applies.

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 states a clear verb and resource: it lists services rendered for a Boxberry shipment. It is distinguishable from siblings like list_cities and list_points by the subject matter, though it does not explicitly contrast itself with them.

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 is provided on when to use this tool versus alternatives such as track or calc_delivery. The description gives no context about the intended scenario or exclusions.

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

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only states the action and input; it does not disclose whether the operation is read-only, what kind of result or status data will be returned, how errors are handled, or whether any side effects occur. This is minimal coverage for an unannotated tool.

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 a single, short, front-loaded sentence that conveys the purpose and identifies the key input. There is no filler, redundancy, or unnecessary detail.

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 one-parameter tool, this is minimally adequate: the agent knows what the tool does and what input to provide. However, with no annotations and no output schema, the complete absence of behavioral or return information leaves the agent guessing about the outcome of a successful call.

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% and the sole parameter tracking_number is already documented in the schema. The description adds no additional meaning beyond restating the parameter concept, so it meets the baseline but does not enhance understanding with examples or format details.

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 operation (tracking) and the resource (Boxberry shipment) with the key input (tracking number). It is unambiguous and distinct from sibling tools like list_cities or calc_delivery, though it is phrased as a noun phrase rather than as an explicit verb+object construction.

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?

The description provides no guidance on when to use this tool versus alternatives, nor any exclusions. The phrase 'by tracking number' weakly implies a use case, but no explicit when-to-use or when-not-to-use information is given.

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

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It only says 'проверка' (check), which weakly implies a read-only lookup, but it does not mention return format, error behavior, external API calls, rate limits, or any side effects.

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 a single, front-loaded sentence with no filler or redundancy. Every word contributes to stating the action and object, making it easy to parse quickly.

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 single-required-parameter tool with clear domain context, the description covers the invocation essentials. However, there is no output schema and no description of what the tool returns, so the agent cannot know whether the result is a simple boolean, a status code, or a structured delivery-availability object.

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 100%: the zip parameter is fully described as 'Почтовый индекс для проверки зоны доставки Boxberry'. The tool description adds no new parameter-level meaning beyond what the schema already provides, which matches the baseline for high coverage.

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 states a specific verb and resource: 'Проверка почтового индекса' (check postal code) for 'доступность доставки Boxberry' (Boxberry delivery availability). This clearly differentiates it from siblings like list_cities, list_points, and calc_delivery, which serve different purposes.

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?

The description gives no guidance on when to use this tool versus alternatives such as calc_delivery or list_cities. There are no explicit conditions, prerequisites, or 'use instead' hints, so an agent must infer usage solely from the tool name.

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