cdek_request_photos

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

No annotations are provided, so the description carries full burden. It discloses the HTTP method (POST), prerequisites, and that it returns a list with links. However, it does not clarify if the operation has side effects (e.g., whether it is read-only despite being a POST) or mention limitations like pagination.

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 succinct: three short sentences covering purpose, prerequisites, and filter requirement, followed by a structured parameter list. No redundant or irrelevant information.

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?

Covers the essential aspects: purpose, prerequisites, filter requirement, and parameter formats. Lacks differentiation from sibling tool cdek_download_photos and does not mention error handling for missing filters, but is adequate given the tool's simplicity and the presence of an output schema.

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% (only names and defaults). The description adds critical meaning: date format YYYY-MM-DD for period_begin/period_end, comma-separated format for cdek_numbers, and the requirement to use at least one filter. This compensates well for the schema's lack of detail.

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 retrieves orders with ready photos and returns links to archives. It distinguishes from siblings like cdek_download_photos by focusing on retrieval of order lists with links rather than downloading files.

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?

Explicitly requires at least one filter (date range or CDEK numbers) and lists prerequisites (photo service and project). Does not explicitly compare to siblings or state when not to use, but provides clear usage context.

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