base_tableList

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

The description discloses the 'persist' behavior (materializing as a volatile table) but does not mention whether the operation is read-only, any permissions required, or performance implications. Without annotations, this is partially adequate but insufficient for full transparency.

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 short and front-loaded with the core purpose. However, it redundantly repeats parameter descriptions already present in the input schema, reducing efficiency. Still, it avoids unnecessary fluff.

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?

The tool has no output schema, so the description should explain return values. It only mentions returning a table name when persist=True, but not the format of the list when persist=False. Missing details like pagination or result limits make it incomplete for a simple list tool.

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 coverage is 100%, so the baseline is 3. The description adds no new meaning beyond what the schema already provides for both parameters; 'Leave empty for all databases' is identical in the description and schema. No additional usage hints or format details are given.

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 tool lists tables and views in a database, with the scope clarified by 'Leave empty for all databases.' The verb 'Lists' and resource 'tables and views' are specific, but it does not explicitly distinguish from siblings like base_databaseList or base_columnDescription.

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?

No guidance on when to use this tool versus alternatives such as base_databaseList or base_tableUsage. The description does not provide context for selecting this tool over siblings, nor does it mention prerequisites or 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.