get_buyer_waybills_ex

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating safe read-only behavior. The description adds no behavioral context beyond what annotations provide, but it does not contradict them. It confirms the listing nature, which aligns with readOnlyHint. No additional side effects or constraints are disclosed.

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 a parenthetical translation, which is concise but lacks essential information such as the tool's extended nature or output behavior. It is front-loaded but does not efficiently communicate all necessary details for an 18-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?

Given the tool has 18 parameters and no output schema, the description is too brief. It does not explain what constitutes a 'buyer waybill', the meaning of 'extended' in the tool name, or how the filters work together. The agent would need to rely heavily on the schema, which may not be sufficient for effective invocation.

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%, meaning all parameters have descriptions in the schema. The description adds no extra meaning beyond the schema; it only highlights the 'confirmation filter' which is already described in the 'is_confirmed' parameter. Thus, baseline score of 3 is appropriate.

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 'List buyer waybills with confirmation filter', providing a specific verb and resource. However, it does not differentiate from the sibling tool 'get_buyer_waybills', which may also list buyer waybills without the confirmation filter. The inclusion of the Georgian translation adds local context but does not aid in differentiation.

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 its siblings, such as 'get_buyer_waybills' or 'get_waybills_ex'. There are no when-to-use or when-not-to-use instructions, leaving the agent to infer based solely on the name and description.

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