base_tableList

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

Annotations already declare readOnlyHint=true and idempotentHint=true. Description adds context about the persist parameter materializing as a volatile table. No additional behavioral details beyond that, which is sufficient given the safety profile.

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?

Multi-line structure with clear main point and parameter details. Not overly verbose, though could be slightly more structured. Front-loaded with tool action.

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?

No output schema, so description should describe return format. It only mentions for persist case. For default list, no output description is provided, leaving the agent unaware of result structure (e.g., columns).

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?

Input schema has 100% description coverage. Description largely repeats schema but adds the clarifying question guidance for database_name, enhancing semantic value beyond schema.

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?

Verb 'List' + resource 'tables and views' + scope 'within a specific Teradata database or schema'. Distinct from sibling tools like base_databaseList (list databases) and base_tableDDL (get DDL).

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?

Explicit guidance on when to pass database_name vs omit, with a caution to ask clarifying question to avoid querying all databases. Lacks comparison to sibling tools but provides clear context.

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