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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds useful behavioral context beyond annotations: it says drafts and published versions are both returned, that six built-in looks are included, and that returned URLs are directly usable by MapLibre. It does not describe ordering or pagination, but for a simple list tool this is minor.

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?

Two short sentences, front-loaded with the resource scope and followed by the key practical detail about MapLibre-compatible URLs. Every sentence earns its place with no filler.

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 no-parameter read-only list tool with full annotation coverage and no output schema, the description is nearly complete: it says what is included and that URLs are directly usable. It could be stronger by noting whether results are paginated or ordered, but no critical information is missing for correct invocation.

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?

The tool has zero parameters, so there is nothing for the description to clarify. Baseline 4 applies because the description appropriately focuses on output content rather than nonexistent inputs.

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 clearly states the resource: workspace styles including drafts and published versions, plus the six built-in looks. It is specific about content, though the verb is implicit from the name 'list_styles' rather than stated directly, and sibling differentiation from tools like 'list_sprites' or 'update_style' is left to the name.

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 description: use this to discover style URLs that MapLibre can consume. However, it does not explicitly say when to use this versus 'create_style', 'update_style', or 'list_sprites', nor does it mention prerequisites or exclusions.

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