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

The annotations already disclose that this is a non-read-only, idempotent, non-destructive write operation. The description adds little beyond restating that metadata is updated; it does not explain partial-patch semantics, how null values clear fields, whether omitted fields remain unchanged, or what 'visibility' means given that no visibility field exists in the schema.

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 description is a single front-loaded sentence with no wasted words. Its brevity is structurally clean, though it leaves too much unsaid rather than being verbose.

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?

Given a complex nested patch object, low schema description coverage, and no output schema, the description is substantially incomplete. It does not explain the patch structure, supported fields, null-clearing behavior, or what changes are returned or confirmed after the update.

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%, and the nested patch object contains many more fields than the description mentions. The description names only title, description, and visibility, while omitting patch semantics and nearly all supported metadata fields. It also references a visibility field not present in the schema, adding confusion rather than meaning.

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 ('Update ... metadata of a geospatial collection'), so the general purpose is clear. However, it scopes the tool to title, description, and visibility, while the schema exposes many more fields and contains no visibility property at all. That mismatch can lead an agent to underestimate or misunderstand the tool's actual capabilities.

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?

There is no guidance on when to use this tool versus relevant siblings such as collection_create, resource_change_visibility, or source_update_metadata. It also does not mention prerequisites like required permissions or ownership. The agent is left to infer usage from the name alone.

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