Bulk export URL

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

Annotations already provide readOnlyHint and openWorldHint. The description adds actionable advice: 'download it outside this server' due to the large ZIP size. This enhances transparency beyond the annotations, though it could mention rate limits or authentication requirements.

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 consists of two efficient sentences: the first states the core purpose, and the second provides a critical behavioral caveat. No redundant information, every word earns its place.

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 description covers the main purpose and a key usage note. However, it is missing clarity on whether 'day' and 'month' are mutually exclusive or what happens when both are omitted (all parameters optional). Output schema may fill gaps, but a small clarification would make the description fully self-contained.

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 high (67%), with clear format descriptions for 'day' and 'month' and an enum for 'format'. The tool description adds no further parameter meaning beyond what the schema already provides, so the 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 the verb ('Builds the URL') and the resource ('official bulk export for one day or month'). It distinguishes the tool from sibling tools like 'search_tenders' and 'get_tender' by focusing on bulk export URL generation.

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 does not provide any guidance on when to use this tool versus alternatives or how to choose between the 'day' and 'month' parameters. It only mentions a precondition ('must already be closed') without explaining the use case for each parameter option.

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