List tables

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

Without annotations, the description discloses the output columns and the optional schema filter. It doesn't mention whether system tables are included, ordering, or permission requirements, which are potential gaps.

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 sentences, direct, no redundant information. Both sentences provide necessary content: purpose and return format.

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 low complexity (one optional parameter, no output schema), the description covers purpose, parameter, and return fields. It is largely complete, though it could mention naming conventions or schema default behavior more explicitly.

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 schema already fully documents the 'schema' parameter (100% coverage). The description adds no new semantic information beyond saying 'optionally filtered to a single schema,' which mirrors the schema description.

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?

Clearly states the tool lists tables in the database, with optional schema filtering. Distinguishes from sibling tools like list_procedures, list_views, and list_functions by the resource 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?

The description implies use for listing tables, and the optional schema parameter provides a use case. However, it does not explicitly contrast with sibling listing tools or state when not to use it.

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