base_tableList

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

Annotations already declare readOnlyHint=true and idempotentHint=true, confirming no side effects. The description adds value by explaining that setting persist=True materializes the result as a volatile table and returns a table name, which is a useful behavioral detail beyond the annotations.

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, with a single line for purpose followed by bullet-style argument explanations. Every sentence is necessary and well-organized. No superfluous 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?

Given the tool's simplicity (2 parameters, no output schema, and annotations covering safety), the description is largely complete. It explains the core function and both parameters. Minor missing detail: it doesn't specify the exact return format when persist=False, but the purpose 'Lists all tables and views' implies a list.

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 baseline is 3. The description repeats the schema's parameter descriptions almost verbatim ('Database name - Leave empty for all databases', 'If True, materializes result...'). It adds no additional meaning beyond what the schema already provides.

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 all tables and views in a database. It uses a specific verb 'Lists' and resource 'tables and views', and distinguishes from siblings like base_databaseList (databases) and base_columnDescription (columns).

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?

There is no explicit guidance on when to use this tool versus alternatives. The purpose is clear, but no conditions or exclusions are provided to help an agent choose between this and other listing tools like base_databaseList or base_tableDDL.

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