gbif_occurrence_download_predicate_builder

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that the output is a predicate consumed by the download API, which is useful context, but says nothing about return format, whether the output must be passed through unchanged, or error behavior for invalid filters.

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?

Two short sentences with no filler, and the core purpose is front-loaded. However, the second sentence largely restates the first ('build a download predicate from simple search parameters' vs 'converts occurrence search filters into the complex predicate format'), so there is mild 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?

For an 8-parameter helper with no output schema, the description should at least characterize the return value (the predicate shape/format) and how it feeds the download tool. It explains the role but leaves the agent uncertain about what it actually produces and how to use it next, which is a real gap for a tool with no 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 description coverage is 100%, so the schema already documents all 8 parameters with examples (year ranges, ISO country codes, WKT winding order, taxonKey semantics). The description contributes no additional parameter meaning beyond what the schema provides, which is the expected baseline here.

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: it builds a download predicate from simple search parameters and converts occurrence search filters into the predicate format required by the download API. This is clearly distinguishable from listing/searching siblings, though it never names the specific download tool whose input it produces (e.g. gbif_occurrence_download_request).

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?

Usage is implied by 'required by the download API', suggesting this runs before a download request, but the description never says when to use this versus other occurrence tools or explicitly names the alternative. No exclusions or prerequisites are given, so the agent must infer the workflow position.

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