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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral detail — trending is recomputed every 6h from recent saves/views plus recency, and trending rows carry rank/type/refId/label — but says nothing about ordering, page sizes, or total counts for other collections. With annotations carrying the safety load, this is a solid mid-range contribution.

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 first sentence is clean and front-loaded, but everything after it is one 15-clause run-on sentence that is hard to scan and would be far clearer as a list. It is dense rather than padded, yet the exhaustive enumeration still omits two enum values, so the length is not fully earning 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?

No output schema exists, and the description only sketches return shape for the trending collection; for the other fourteen it says nothing about row fields, ordering, or pagination/total counts, and it never mentions the q or limit parameters. Combined with the undescribed library/jobs enum values, an agent can pick a collection but not predict what comes back.

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 100%, so the baseline is 3, but the description goes further by explaining what each enum value actually contains (e.g. artifacts include versions, licenses, provenance, reproducibility status; field_data is the vetted measured well dataset) — real semantic value beyond "Which collection to list." However the enum has 16 values and "library" and "jobs" are never described, leaving two options unexplained.

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?

Opens with a specific verb and resource ("List records from a SuperhotGeo public collection") and enumerates what each collection holds, so the agent knows exactly what the tool retrieves. It never contrasts itself with the sibling tools it clearly overlaps with (search, search_library, get_resource, search_wells), leaving disambiguation to the agent.

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 only implied by the verb "list" plus the per-collection descriptions; there is no statement of when to choose this over search, search_library, or get_resource. No prerequisites, exclusions, or alternative routing are given, so the agent must infer the list-vs-search split.

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