list_workspace_contents

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that an omitted workspace falls back to the project's default geodatabase, but it does not state that the operation is read-only, whether listing is recursive, or how 'datasets' is scoped (feature classes, tables, rasters, etc.).

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 with no filler, and the core action is front-loaded before the default-workspace note. Every sentence carries information.

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?

An output schema exists, so return values need not be explained. The description covers the basic scope and default workspace for a four-parameter read tool, though it could clarify what categories of datasets are included and that limits apply per category.

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 the schema fully documents limit, wildcard, workspace, and include_details. The description only reinforces the workspace default and adds no syntax or format details beyond that baseline.

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 states a specific verb and resource: listing datasets inside a geodatabase or folder. This clearly distinguishes the tool from unrelated siblings like get_features or create_table. However, it does not differentiate itself from closer siblings such as list_folder or search_data, which could also enumerate spatial content.

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 only usage-related statement is that the workspace parameter defaults to the project's default geodatabase. There is no guidance on when to choose this tool over list_folder, search_data, or describe_dataset, nor are any exclusions or prerequisites stated.

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