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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds nothing beyond that — it does not say whether 'patch' is a partial merge (fields omitted are left untouched) or a full replacement, nor how conflicting concurrent edits behave.

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 focused sentence with no filler, and the core action is front-loaded. It is arguably too terse for a nested-15-field mutation, but there is no wasted text.

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 complex mutating tool with a nested patch object, no output schema, and 0% schema description coverage, a one-line description is insufficient. It fails to explain partial-update semantics, null-clearing behavior (several fields are nullable), or permission requirements.

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%, so the description carries the burden for the nested 'patch' object, yet it names only title and description (two of ~15 fields) and references a nonexistent 'visibility' field. It omits licences, tags, country codes, review status/dates, and other patchable metadata, leaving the agent to reverse-engineer semantics from raw schema.

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 (Update) and resource (collection metadata of a geospatial collection), which cleanly distinguishes it from siblings like geobble_source_update_metadata. However, it claims to update only 'title, description, and visibility,' while the patch schema exposes ~15 fields and contains no 'visibility' property at all, so the stated scope is both under- and mis-stated.

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 gives no when-to-use guidance, no prerequisites (e.g., ownership/permission to edit a collection), and does not name alternatives such as geobble_resource_change_visibility for visibility changes or geobble_collection_create. The agent must infer usage entirely.

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