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

Annotations already declare this is a non-read-only, non-destructive, non-open-world write, so the safety profile is covered. The description adds only the soft constraint of creating 'under an accessible account' — no idempotency behavior, slug-uniqueness failure mode, or persistence consequences are disclosed.

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?

A single well-formed sentence with the action front-loaded and no filler. It is efficient, though the clause between the dashes is the only reason it is not maximally tight.

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 tool whose payload is a deep nested object with zero schema documentation and no output schema, one sentence is far too thin. Required fields, slug format constraints, and the meaning of the owner handle are all left to the schema alone, which documents nothing.

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 0% for two parameters, one of which is a nested object with ~17 fields (slug pattern, enums, dates, tags) that the description never mentions. The phrase about a 'curated group of geospatial datasets' only loosely gestures at the collection payload and leaves ownerHandle entirely implicit.

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?

Specific verb (create) plus resource (collection) and a gloss of what a collection is (a curated group of geospatial datasets), which disambiguates it from generic create tools. It does not distinguish itself from the nearby collection_update_metadata sibling, so it stops short of a 5.

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 when-to-use guidance, no prerequisites, no mention of alternatives. 'Under an accessible account' hints at an ownership requirement but never states what makes an account accessible or what to do if it is not.

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