list_layers

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

With no annotations provided, the description carries full burden. It reveals the return format (ListLayersOutput JSON with workspace, layers, elapsed_seconds) and parameter behavior. It does not mention side effects, authentication, or performance limits, but it is transparent about being a read operation on a file geodatabase.

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 concise and well-structured, using a docstring format with clear Args and Returns sections. It front-loads the main purpose and includes no unnecessary words.

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 the tool's simplicity and the presence of an output schema, the description is largely complete. It covers inputs and output format. Minor gaps include not specifying whether the list is recursive or limited to top-level datasets, or any restrictions on workspace roots.

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 explains each parameter fully: workspace is an absolute path to a .gdb, dataset_filter is an optional wildcard. This adds significant meaning beyond the schema's type declarations.

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 it lists feature classes, tables, and rasters inside a file geodatabase. This is a specific verb-resource combination that distinguishes it from siblings like list_layers_in_map (which lists layers in a map document) and other geodatabase tools.

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 provides clear context for when to use the tool (to list contents of a file geodatabase). It does not explicitly state when not to use it or mention alternatives, but the context is sufficient and the tool's scope is well-defined.

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