list_tables

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

With no annotations, the description adds useful behavior: it clarifies that an empty workspace falls back to the current workspace. However, it does not state the return shape (covered by output schema), whether results are ordered, or any path/error behavior, so it only partially carries the behavioral disclosure burden.

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 compact and front-loaded with the tool's purpose, followed by a minimal args list. Every sentence adds information, and there is no filler or repetition of schema content.

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 optional-parameter list tool with an output schema, the description covers the key invocation details and workspace fallback behavior. It could be more complete by explicitly directing agents to list_feature_classes/list_rasters for other data types, but that gap is minor.

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 has only titles and defaults (0% coverage). The description compensates by defining workspace as a path defaulting to the current workspace and pattern as a wildcard filter. This adds meaning that the structured schema alone does not provide.

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?

States a specific verb ('List') and resource ('standalone tables in a workspace') with concrete examples (GDB tables, DBF files). This distinguishes the tool from sibling listers like list_feature_classes and list_rasters by data type.

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 context is implied by the phrase 'standalone tables' and the examples, but there is no explicit when-to-use or when-not-to-use guidance or any mention of alternatives such as list_feature_classes or list_layers. An agent must infer the selection criteria from the resource type.

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