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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context that results are user-contributed and openly licensed, which matters for downstream reuse, but says nothing about pagination behavior or result ordering defaults beyond what the schema lists.

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?

Three short sentences, front-loaded with the core action and resource. The middle sentence about open licenses is slightly redundant with 'community-submitted' but does add licensing information, so it mostly earns 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?

With five optional parameters, no required fields, and no output schema, an agent knows enough to call it, but nothing is said about the shape of returned layer records or how pagination interacts with limit/offset. Adequate but with clear gaps for a listing tool.

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 100%, so q, sort, limit, offset and category are all documented with defaults. The description only restates the category and name-search cases, adding no syntax, matching behavior, or interaction details beyond the schema — baseline 3 applies.

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 ('List community-submitted geo layers') and the qualifier 'community-submitted' implicitly separates it from list_layers, which would return the non-contributed catalog. It stops short of naming that sibling, so the distinction is inferable rather than 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?

'Filter by category or search by name' hints at the two main usage modes, but there is no explicit when-to-use guidance relative to list_layers, query_layer, or get_layer_detail. An agent must reason from the word 'community-submitted' alone to decide which listing tool to call.

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