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

Goes well beyond the annotations by disclosing the side effects: the remote file is downloaded, stored and made visible to the project team, and nothing existing is deleted or overwritten. It also reveals that the request is asynchronous — Biohotspot checks the upload afterwards and may require action in the Uploads tab — which an agent could not infer from destructiveHint=false alone.

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 purpose and the side-effect warning are front-loaded in the first two clauses, so an agent can decide quickly. It is dense rather than bloated, though the illustrative list ('a survey, a map') and the multi-clause parenthetical cost some readability.

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 a write tool with no output schema, it covers side effects, permission requirements, async status tracking and input constraints — enough to invoke it safely. The remaining gap is what the call returns (an id or job handle) and how the post-upload 'checks' manifest, which the agent must discover via list_project_data.

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 only 33% (source and licence only), so the description must compensate, and it does add real meaning for 'url': public link, accepted formats, 200 MB ceiling. However, 'year' and 'title' get no explanation at all, and it does not say whether the URL must be anonymously reachable, so the gap for four of six parameters is only partly filled.

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?

States a specific verb and resource (add data to a project) plus the input channel (a public download link) and the accepted formats and size cap. This cleanly separates it from read-side siblings such as list_project_data, get_project and find_layers, which never mutate a project.

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?

Gives concrete use cases ('your own model's output, a survey, a map') and an explicit follow-up route: check processing with list_project_data and complete any prompts in the Uploads tab. It also states the permission prerequisite (owner or editor rights). It stops short of naming when NOT to use it (e.g. adding local files or existing platform layers).

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