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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the returned basemap categories, which is useful context, but it does not explain project scoping, authorization needs, or return shape, leaving meaningful behavioral gaps.

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, front-loaded sentence with no wasted text. It states the verb, resource, and valid values immediately.

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 simple listing tool with full schema coverage and rich safety annotations, the description is mostly sufficient. However, it never explains how the 'project' is identified when there is no project parameter, and with no output schema it could better indicate what the response contains beyond the category names.

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% and both parameters are enums with documented values, so the schema carries the parameter burden. The description's list of light, dark, vector, raster, and DEM loosely maps to those enum filters but adds little beyond the 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?

The description uses a specific verb ('List') and resource ('valid basemaps available to a project') and enumerates the categories returned. It clearly tells an agent what the tool does, though it does not explicitly contrast with the obvious sibling project_set_basemap.

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 implied by the read-only listing purpose, but the description gives no explicit when-to-use, when-not-to-use, or alternative (e.g., project_set_basemap) guidance. An agent must infer that this is a discovery call.

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