list_layers

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

No annotations are provided, so the description carries the full burden. It mentions the tool lists layers and returns information dictionaries, but lacks details on permissions required, pagination behavior, rate limits, error conditions, or what fields the dictionaries contain. This is a significant gap for a tool with no annotation coverage.

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 front-loaded with the core purpose, followed by clear Arg and Returns sections in a structured format. Every sentence earns its place with no redundant information, making it efficient and easy to parse.

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 no annotations, 0% schema description coverage, and no output schema, the description is moderately complete. It covers the purpose and parameter semantics adequately but lacks behavioral details like permissions or error handling. For a simple read operation, this is acceptable but not thorough.

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 must compensate. It documents the single parameter 'workspace' as optional for filtering, adding meaning beyond the schema's basic type and title. However, it doesn't explain the format of workspace names or provide examples, leaving some ambiguity.

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 verb 'List' and resource 'layers in GeoServer', with optional workspace filtering. It distinguishes the tool from siblings like 'get_layer_info' (detailed info) and 'list_workspaces' (different resource). However, it doesn't explicitly contrast with 'query_features' (data querying vs metadata listing).

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 implies usage for listing layers, optionally filtered by workspace, but doesn't explicitly state when to use this versus alternatives like 'get_layer_info' (for detailed info on a specific layer) or 'query_features' (for querying layer data). No guidance on prerequisites or exclusions is provided.

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