cdek_waybill

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

No annotations are present, so the description must cover behavioral traits. It mentions saving a PDF to a path but omits side effects (e.g., overwriting), authentication needs, rate limits, or what happens on error. The POST method is noted but without additional context.

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 concise: two sentences and a simple argument explanation. It is front-loaded with the core action and uses a structured format. Every sentence provides essential information without redundancy.

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's simplicity (2 parameters, no nested objects) and the presence of an output schema, the description covers the main purpose and parameter meanings. Missing details like expected return or error handling are acceptable for a straightforward file-download tool.

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 the description compensates by explaining each parameter: cdek_number is a CDEK tracking number, output_path is an absolute path to save the PDF. This adds clear meaning beyond the schema's bare type and title, though constraints like file extension or size are missing.

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 tool forms and downloads a receipt (waybill) in PDF format, specifying the HTTP method and endpoint. The verb 'формирует и скачивает' and resource 'квитанции к заказу' are specific, and the tool is distinct from siblings like cdek_barcode and cdek_label which handle other print formats.

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. The description merely states what it does, without mentioning prerequisites, exclusions, or comparisons to sibling tools like cdek_label or cdek_barcode.

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